From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw100709 [PATCH v4] ethdev: replace bit shifts with macros
Date: Thu, 7 Oct 2021 17:49:43 +0200 (CEST) [thread overview]
Message-ID: <20211007154943.4FFD0120E00@dpdk.org> (raw)
In-Reply-To: <20211007154847.864237-1-thomas@monjalon.net>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/100709
_coding style OK_
next parent reply other threads:[~2021-10-07 15:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211007154847.864237-1-thomas@monjalon.net>
2021-10-07 15:49 ` checkpatch [this message]
2021-10-07 16:38 ` [dpdk-test-report] |SUCCESS| pw100709 [dpdk-dev] " 0-day Robot
2021-10-07 16:22 [dpdk-test-report] |SUCCESS| pw100709 [PATCH] [v4] " dpdklab
2021-10-07 16:26 dpdklab
2021-10-07 16:28 dpdklab
2021-10-07 16:32 dpdklab
2021-10-07 16:36 dpdklab
2021-10-07 16:37 dpdklab
2021-10-07 16:37 dpdklab
2021-10-07 16:38 dpdklab
2021-10-07 16:50 dpdklab
2021-10-07 16:52 dpdklab
2021-10-07 18:05 dpdklab
2021-10-07 18:20 dpdklab
2021-10-07 18:33 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=20211007154943.4FFD0120E00@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).