From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw108399 [PATCH v1] net/iavf: fix function pointer in multi-process
Date: Mon, 28 Feb 2022 10:57:05 +0100 (CET) [thread overview]
Message-ID: <20220228095705.0BDC51234A0@dpdk.org> (raw)
In-Reply-To: <20220228094859.239717-1-stevex.yang@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/108399
_coding style OK_
next parent reply other threads:[~2022-02-28 9:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220228094859.239717-1-stevex.yang@intel.com>
2022-02-28 9:57 ` checkpatch [this message]
2022-02-28 11:58 ` 0-day Robot
2022-03-01 3:47 |SUCCESS| pw108399 [PATCH] [v1] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-02-28 19:09 dpdklab
2022-02-28 18:50 dpdklab
2022-02-28 17:36 dpdklab
2022-02-28 13:09 dpdklab
2022-02-28 11:56 dpdklab
2022-02-28 11:50 dpdklab
2022-02-28 11:39 dpdklab
2022-02-28 11:32 dpdklab
2022-02-28 11:23 dpdklab
2022-02-28 11:21 dpdklab
2022-02-28 11:09 dpdklab
2022-02-28 10:56 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=20220228095705.0BDC51234A0@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).