From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Viacheslav Galaktionov <viacheslav.galaktionov@arknetworks.am>
Subject: |WARNING| pw122474 [PATCH] mailmap: update contributor entry
Date: Tue, 24 Jan 2023 12:09:40 +0100 (CET) [thread overview]
Message-ID: <20230124110940.B5132123D76@dpdk.org> (raw)
In-Reply-To: <20230124110801.11726-1-viacheslav.galaktionov@arknetworks.am>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/122474
_coding style issues_
WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
total: 0 errors, 1 warnings, 8 lines checked
Viacheslav Galaktionov mail differs from primary mail, please fix the commit message or update .mailmap.
next parent reply other threads:[~2023-01-24 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230124110801.11726-1-viacheslav.galaktionov@arknetworks.am>
2023-01-24 11:09 ` checkpatch [this message]
2023-01-24 12:00 ` |SUCCESS| " 0-day Robot
2023-01-25 1:57 ` qemudev
2023-01-25 2:01 ` qemudev
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=20230124110940.B5132123D76@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=viacheslav.galaktionov@arknetworks.am \
/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).