From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <smadarf@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw90878 [PATCH v2] net/octeontx2: support flow action port id
Date: Thu, 8 Apr 2021 12:26:09 +0200 (CEST) [thread overview]
Message-ID: <20210408102609.D4E93120D42@dpdk.org> (raw)
In-Reply-To: <20210408102113.5545-1-smadarf@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/90878
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
next parent reply other threads:[~2021-04-08 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210408102113.5545-1-smadarf@marvell.com>
2021-04-08 10:26 ` checkpatch [this message]
2021-04-08 11:58 ` [dpdk-test-report] |SUCCESS| pw90878 [dpdk-dev] " 0-day Robot
2021-04-08 12:55 ` [dpdk-test-report] |SUCCESS| pw90878 " 0-day Robot
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=20210408102609.D4E93120D42@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=smadarf@marvell.com \
--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).