From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw131399 [PATCH] maintainers: update for gro and gso
Date: Wed, 13 Sep 2023 15:46:12 +0200 (CEST) [thread overview]
Message-ID: <20230913134612.4688F120802@dpdk.org> (raw)
In-Reply-To: <tencent_A410C2E83B08BF05402B62DB71371E0A010A@qq.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/131399
_coding style OK_
next prev parent reply other threads:[~2023-09-13 13:46 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_A410C2E83B08BF05402B62DB71371E0A010A@qq.com>
2023-09-13 13:32 ` qemudev
2023-09-13 13:36 ` qemudev
2023-09-13 13:46 ` checkpatch [this message]
2023-09-13 14:39 ` 0-day Robot
2023-09-14 18:15 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-09-13 15:56 dpdklab
2023-09-13 15:43 dpdklab
2023-09-13 15:29 dpdklab
2023-09-13 15:26 dpdklab
2023-09-13 15:25 dpdklab
2023-09-13 15:24 dpdklab
2023-09-13 15:23 dpdklab
2023-09-13 15:23 dpdklab
2023-09-13 15:23 dpdklab
2023-09-13 15:21 dpdklab
2023-09-13 15:21 dpdklab
2023-09-13 15:14 dpdklab
2023-09-13 15:13 dpdklab
2023-09-13 15:12 dpdklab
2023-09-13 15:10 dpdklab
2023-09-13 15:09 dpdklab
2023-09-13 15:08 dpdklab
2023-09-13 15:08 dpdklab
2023-09-13 15:07 dpdklab
2023-09-13 15:06 dpdklab
2023-09-13 15:05 dpdklab
2023-09-13 15:05 dpdklab
2023-09-13 15:05 dpdklab
2023-09-13 15:05 dpdklab
2023-09-13 14:59 dpdklab
2023-09-13 14:58 dpdklab
2023-09-13 14:49 dpdklab
2023-09-13 14:48 dpdklab
2023-09-13 14:48 dpdklab
2023-09-13 14:48 dpdklab
2023-09-13 14:48 dpdklab
2023-09-13 14:48 dpdklab
2023-09-13 14:47 dpdklab
2023-09-13 14:47 dpdklab
2023-09-13 14:47 dpdklab
2023-09-13 14:47 dpdklab
2023-09-13 14:47 dpdklab
2023-09-13 14:47 dpdklab
2023-09-13 14:47 dpdklab
2023-09-13 14:47 dpdklab
2023-09-13 14:46 dpdklab
2023-09-13 14:44 dpdklab
2023-09-13 14:44 dpdklab
2023-09-13 14:44 dpdklab
2023-09-13 14:44 dpdklab
2023-09-13 14:44 dpdklab
2023-09-13 14:44 dpdklab
2023-09-13 14:37 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=20230913134612.4688F120802@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).