[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0987e828-f7c3-4d11-ab1b-a671d091fbea@web.de>
Date: Fri, 26 Jul 2024 10:30:20 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Zhu Jun <zhujun2@...s.chinamobile.com>, linux-kselftest@...r.kernel.org,
Chunyan Zhang <zhang.lyra@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>, Andy Lutomirski
<luto@...capital.net>, Kees Cook <kees@...nel.org>,
Shuah Khan <shuah@...nel.org>, Will Drewry <wad@...omium.org>
Subject: Re: [PATCH v5] tools/testing: Fix the wrong format specifier
> The format specifier in fprintf is "%u", that "%u" should use
> unsigned int type instead.
* Please improve the change description with imperative wordings.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10#n94
* Would you like to add any tags (like “Fixes” and “Cc”) accordingly?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10#n145
* How good does the summary phrase fit to your proposal?
> the problem is discovered by reading code.
How do you think about to detect such change possibilities by more systematic
source code analyses?
Regards,
Markus
Powered by blists - more mailing lists