From: Simon Horman <horms@kernel.org>
To: Zhu Jun <zhujun2@cmss.chinamobile.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
hawk@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/net:Fix the wrong format specifier
Date: Wed, 25 Sep 2024 20:59:59 +0100 [thread overview]
Message-ID: <20240925195959.GZ4029621@kernel.org> (raw)
In-Reply-To: <20240925195354.GY4029621@kernel.org>
On Wed, Sep 25, 2024 at 08:53:54PM +0100, Simon Horman wrote:
> On Wed, Sep 25, 2024 at 01:55:24AM -0700, Zhu Jun wrote:
> > The format specifier of "unsigned int" in printf() should be "%u", not
> > "%d".
> >
> > Signed-off-by: Zhu Jun <zhujun2@cmss.chinamobile.com>
>
> Hi Zhu Jun,
>
> Thanks for your patch.
>
> While this change looks good to me it looks like it is for net-next.
> Currently net-next is closed for the v6.12 merge window. So please
> repost this patch once it reopens, after v6.12-rc1 has been released.
> I expect that to happen early next week.
>
> Also, please explicitly target net-next patches for that tree like this:
>
> Subject: [PATCH net-next]
>
> For reference, netdev processes are documented here:
> https://docs.kernel.org/process/maintainer-netdev.html
Sorry, one more thing, looking at git history I think the prefix
for the patch should be 'tools: ynl: '. So perhaps:
Subject: [PATCH net-next] tools: ynl: correct page-pool stat format specifier
prev parent reply other threads:[~2024-09-25 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 8:55 [PATCH] tools/net:Fix the wrong format specifier Zhu Jun
2024-09-25 19:53 ` Simon Horman
2024-09-25 19:59 ` Simon Horman [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=20240925195959.GZ4029621@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=zhujun2@cmss.chinamobile.com \
/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).