From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fengnan Chang <changfengnan@bytedance.com>
Subject: |WARNING| pw123655 [PATCH] malloc: fix malloc performance may becomes worse as the number of malloc increases
Date: Fri, 10 Feb 2023 07:30:42 +0100 (CET) [thread overview]
Message-ID: <20230210063042.AFC6F121E50@dpdk.org> (raw)
In-Reply-To: <20230210063022.52171-1-changfengnan@bytedance.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/123655
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#104:
it will search free_head[2] from begin, with the number of malloc increases,
total: 0 errors, 1 warnings, 26 lines checked
Fengnan Chang <changfengnan@bytedance.com> is unknown, please fix the commit message or update .mailmap.
next prev parent reply other threads:[~2023-02-10 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230210063022.52171-1-changfengnan@bytedance.com>
2023-02-10 6:19 ` |SUCCESS| " qemudev
2023-02-10 6:23 ` qemudev
2023-02-10 6:30 ` checkpatch [this message]
2023-02-13 15:41 ` 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=20230210063042.AFC6F121E50@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=changfengnan@bytedance.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).