From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Prateek Agarwal <pratekag@gmail.com>
Subject: [dpdk-test-report] |WARNING| pw83822 [PATCH] Made i40 header CPP compatible using extern "C". Library headers work directly in cpp code. Linking errors
Date: Sat, 7 Nov 2020 10:01:12 +0100 (CET) [thread overview]
Message-ID: <20201107090112.03098354D@dpdk.org> (raw)
In-Reply-To: <20201107090038.12802-1-pratekag@gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/83822
_coding style issues_
WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
total: 0 errors, 1 warnings, 0 checks, 18 lines checked
next parent reply other threads:[~2020-11-07 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201107090038.12802-1-pratekag@gmail.com>
2020-11-07 9:01 ` checkpatch [this message]
2020-11-07 11:27 ` [dpdk-test-report] |SUCCESS| pw83822 Made i40 header CPP compatible using extern \"C\". Library headers work directly in cpp code. Linking errors thrown due to the absence of this change in i40e pmd header does not help in resolving the problem. I needed this header directly to use DDP feature present in the NIC 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=20201107090112.03098354D@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pratekag@gmail.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).