From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw124589 [PATCH] kni: fix build with Linux 6.3
Date: Tue, 28 Feb 2023 18:30:48 +0100 (CET) [thread overview]
Message-ID: <20230228173048.0D115120D89@dpdk.org> (raw)
In-Reply-To: <20230228172909.2054386-1-ferruh.yigit@amd.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/124589
_coding style OK_
next parent reply other threads:[~2023-02-28 17:30 UTC|newest]
Thread overview: 215+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230228172909.2054386-1-ferruh.yigit@amd.com>
2023-02-28 17:30 ` checkpatch [this message]
2023-02-28 19:20 ` 0-day Robot
2023-03-01 8:12 ` qemudev
2023-03-01 8:13 ` qemudev
2023-02-28 22:21 dpdklab
2023-02-28 22:22 dpdklab
2023-02-28 22:23 dpdklab
2023-02-28 22:29 dpdklab
2023-02-28 22:36 dpdklab
2023-02-28 22:50 dpdklab
2023-02-28 23:04 dpdklab
2023-02-28 23:18 dpdklab
2023-02-28 23:18 dpdklab
2023-02-28 23:21 dpdklab
2023-02-28 23:22 dpdklab
2023-02-28 23:25 dpdklab
2023-02-28 23:29 dpdklab
2023-02-28 23:31 dpdklab
2023-02-28 23:34 dpdklab
2023-02-28 23:40 dpdklab
2023-02-28 23:41 dpdklab
2023-02-28 23:44 dpdklab
2023-02-28 23:44 dpdklab
2023-02-28 23:45 dpdklab
2023-02-28 23:46 dpdklab
2023-02-28 23:48 dpdklab
2023-02-28 23:55 dpdklab
2023-02-28 23:59 dpdklab
2023-03-01 0:00 dpdklab
2023-03-01 0:03 dpdklab
2023-03-01 0:04 dpdklab
2023-03-01 0:08 dpdklab
2023-03-01 0:15 dpdklab
2023-03-01 0:19 dpdklab
2023-03-01 0:19 dpdklab
2023-03-01 0:19 dpdklab
2023-03-01 0:23 dpdklab
2023-03-01 0:27 dpdklab
2023-03-01 0:27 dpdklab
2023-03-01 0:31 dpdklab
2023-03-01 0:35 dpdklab
2023-03-01 0:39 dpdklab
2023-03-01 0:42 dpdklab
2023-03-01 0:46 dpdklab
2023-03-01 0:47 dpdklab
2023-03-01 0:52 dpdklab
2023-03-01 0:55 dpdklab
2023-03-01 0:57 dpdklab
2023-03-01 1:00 dpdklab
2023-03-01 1:04 dpdklab
2023-03-01 1:06 dpdklab
2023-03-01 1:07 dpdklab
2023-03-01 1:11 dpdklab
2023-03-01 1:15 dpdklab
2023-03-01 1:15 dpdklab
2023-03-01 1:26 dpdklab
2023-03-01 1:26 dpdklab
2023-03-01 1:28 dpdklab
2023-03-01 1:30 dpdklab
2023-03-01 1:33 dpdklab
2023-03-01 1:34 dpdklab
2023-03-01 1:38 dpdklab
2023-03-01 1:40 dpdklab
2023-03-01 1:48 dpdklab
2023-03-01 1:49 dpdklab
2023-03-01 1:56 dpdklab
2023-03-01 1:59 dpdklab
2023-03-01 2:01 dpdklab
2023-03-01 2:11 dpdklab
2023-03-01 2:18 dpdklab
2023-03-01 2:30 dpdklab
2023-03-01 2:31 dpdklab
2023-03-01 2:47 dpdklab
2023-03-01 2:51 dpdklab
2023-03-01 2:59 dpdklab
2023-03-01 3:04 dpdklab
2023-03-01 3:15 dpdklab
2023-03-01 3:24 dpdklab
2023-03-01 3:27 dpdklab
2023-03-01 3:36 dpdklab
2023-03-01 3:44 dpdklab
2023-03-01 3:56 dpdklab
2023-03-01 3:57 dpdklab
2023-03-01 4:09 dpdklab
2023-03-01 4:13 dpdklab
2023-03-01 4:26 dpdklab
2023-03-01 4:29 dpdklab
2023-03-01 4:29 dpdklab
2023-03-01 4:35 dpdklab
2023-03-01 4:41 dpdklab
2023-03-01 4:43 dpdklab
2023-03-01 4:45 dpdklab
2023-03-01 4:56 dpdklab
2023-03-01 5:01 dpdklab
2023-03-01 5:06 dpdklab
2023-03-01 5:08 dpdklab
2023-03-01 5:14 dpdklab
2023-03-01 5:39 dpdklab
2023-03-01 5:41 dpdklab
2023-03-01 5:53 dpdklab
2023-03-01 6:20 dpdklab
2023-03-01 6:41 dpdklab
2023-03-01 6:48 dpdklab
2023-03-01 7:09 dpdklab
2023-03-01 7:40 dpdklab
2023-03-01 9:13 dpdklab
2023-03-01 9:14 dpdklab
2023-03-01 9:15 dpdklab
2023-03-01 9:17 dpdklab
2023-03-01 9:17 dpdklab
2023-03-01 9:18 dpdklab
2023-03-01 9:19 dpdklab
2023-03-01 9:19 dpdklab
2023-03-01 9:26 dpdklab
2023-03-01 9:28 dpdklab
2023-03-01 9:30 dpdklab
2023-03-01 9:35 dpdklab
2023-03-01 9:52 dpdklab
2023-03-01 9:52 dpdklab
2023-03-01 9:56 dpdklab
2023-03-01 10:00 dpdklab
2023-03-01 10:01 dpdklab
2023-03-01 10:02 dpdklab
2023-03-01 10:05 dpdklab
2023-03-01 10:07 dpdklab
2023-03-01 10:08 dpdklab
2023-03-01 10:09 dpdklab
2023-03-01 10:18 dpdklab
2023-03-01 10:21 dpdklab
2023-03-01 10:23 dpdklab
2023-03-01 10:40 dpdklab
2023-03-01 10:40 dpdklab
2023-03-01 10:43 dpdklab
2023-03-01 10:45 dpdklab
2023-03-01 10:46 dpdklab
2023-03-01 10:53 dpdklab
2023-03-01 10:54 dpdklab
2023-03-01 10:57 dpdklab
2023-03-01 11:02 dpdklab
2023-03-01 11:05 dpdklab
2023-03-01 11:06 dpdklab
2023-03-01 11:08 dpdklab
2023-03-01 11:09 dpdklab
2023-03-01 11:13 dpdklab
2023-03-01 11:25 dpdklab
2023-03-01 11:25 dpdklab
2023-03-01 11:40 dpdklab
2023-03-01 11:45 dpdklab
2023-03-01 11:47 dpdklab
2023-03-01 11:49 dpdklab
2023-03-01 11:50 dpdklab
2023-03-01 11:56 dpdklab
2023-03-01 11:56 dpdklab
2023-03-01 11:58 dpdklab
2023-03-01 11:58 dpdklab
2023-03-01 11:59 dpdklab
2023-03-01 12:01 dpdklab
2023-03-01 12:29 dpdklab
2023-03-01 12:31 dpdklab
2023-03-01 12:31 dpdklab
2023-03-01 12:33 dpdklab
2023-03-01 12:34 dpdklab
2023-03-01 12:34 dpdklab
2023-03-01 12:35 dpdklab
2023-03-01 12:36 dpdklab
2023-03-01 12:44 dpdklab
2023-03-01 12:51 dpdklab
2023-03-01 12:53 dpdklab
2023-03-01 12:57 dpdklab
2023-03-01 12:59 dpdklab
2023-03-01 13:04 dpdklab
2023-03-01 13:13 dpdklab
2023-03-01 13:17 dpdklab
2023-03-01 13:17 dpdklab
2023-03-01 13:18 dpdklab
2023-03-01 13:29 dpdklab
2023-03-01 13:30 dpdklab
2023-03-01 13:39 dpdklab
2023-03-01 13:40 dpdklab
2023-03-01 13:47 dpdklab
2023-03-01 13:48 dpdklab
2023-03-01 13:50 dpdklab
2023-03-01 13:51 dpdklab
2023-03-01 13:52 dpdklab
2023-03-01 13:52 dpdklab
2023-03-01 14:10 dpdklab
2023-03-01 14:22 dpdklab
2023-03-01 14:25 dpdklab
2023-03-01 14:27 dpdklab
2023-03-01 14:27 dpdklab
2023-03-01 14:27 dpdklab
2023-03-01 14:29 dpdklab
2023-03-01 14:30 dpdklab
2023-03-01 14:31 dpdklab
2023-03-01 14:41 dpdklab
2023-03-01 14:43 dpdklab
2023-03-01 14:52 dpdklab
2023-03-01 14:54 dpdklab
2023-03-01 15:02 dpdklab
2023-03-01 15:12 dpdklab
2023-03-01 15:13 dpdklab
2023-03-01 15:13 dpdklab
2023-03-01 15:14 dpdklab
2023-03-01 15:21 dpdklab
2023-03-01 15:31 dpdklab
2023-03-01 15:31 dpdklab
2023-03-01 15:34 dpdklab
2023-03-01 15:36 dpdklab
2023-03-01 15:38 dpdklab
2023-03-01 15:40 dpdklab
2023-03-01 15:44 dpdklab
2023-03-01 15:48 dpdklab
2023-03-01 15:54 dpdklab
2023-03-01 15:57 dpdklab
2023-03-01 15:57 dpdklab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230228173048.0D115120D89@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).