From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Didier Pallard <didier.pallard@6wind.com>
Subject: |WARNING| pw122179 [RFC] Fix cryptodev socket id for devices on unknown NUMA node
Date: Tue, 17 Jan 2023 11:17:36 +0100 (CET) [thread overview]
Message-ID: <20230117101736.140E5123659@dpdk.org> (raw)
In-Reply-To: <20230117101646.2521875-1-didier.pallard@6wind.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/122179
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#78:
https://git.dpdk.org/dpdk/commit/?id=7dcd73e37965ba0bfa430efeac362fe183ed0ae2
total: 0 errors, 1 warnings, 10 lines checked
prev parent reply other threads:[~2023-01-17 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230117101646.2521875-1-didier.pallard@6wind.com>
2023-01-17 10:09 ` |SUCCESS| " qemudev
2023-01-17 10:13 ` qemudev
2023-01-17 10:17 ` checkpatch [this message]
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=20230117101736.140E5123659@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=didier.pallard@6wind.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).