From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Robin Jarry <rjarry@redhat.com>
Subject: |WARNING| pw120196 [PATCH v2 2/4] eal: allow applications to report their cpu cycles utilization
Date: Mon, 28 Nov 2022 10:00:35 +0100 (CET) [thread overview]
Message-ID: <20221128090035.DCD0212230D@dpdk.org> (raw)
In-Reply-To: <20221128085935.161671-3-rjarry@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/120196
_coding style issues_
<dev-bounces@dpdk.org> is unknown, please fix the commit message or update .mailmap.
Robin Jarry mail differs from primary mail, please fix the commit message or update .mailmap.
<20221128085935.161671-3-rjarry@redhat.com> is unknown, please fix the commit message or update .mailmap.
<20221128085935.161671-1-rjarry@redhat.com> is unknown, please fix the commit message or update .mailmap.
<20221123102612.1688865-1-rjarry@redhat.com> is unknown, please fix the commit message or update .mailmap.
<mailto:dev@dpdk.org> is unknown, please fix the commit message or update .mailmap.
<mailto:dev-request@dpdk.org?subject=help> is unknown, please fix the commit message or update .mailmap.
parent reply other threads:[~2022-11-28 9:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20221128085935.161671-3-rjarry@redhat.com>]
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=20221128090035.DCD0212230D@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rjarry@redhat.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).