From: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel@collabora.com, Andy Whitcroft <apw@canonical.com>,
Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>
Subject: Re: [PATCH] checkpatch: warn for p0 patch only if prefix is not b
Date: Tue, 11 Jan 2022 12:47:26 +0200 [thread overview]
Message-ID: <ff6e3942-24e4-25ec-946c-cc6301ebf260@collabora.com> (raw)
In-Reply-To: <CAKXUXMyepnLO=jLPciG5mWvTxbQGR+1PaeYs1_c+-t3hFAEhNg@mail.gmail.com>
On 11.01.22 12:18, Lukas Bulwahn wrote:
> Dafna,
>
> On Mon, Jan 10, 2022 at 9:06 PM Dafna Hirschfeld
> <dafna.hirschfeld@collabora.com> wrote:
>>
>> It might be that file 'b' happens to exit. In that
>> case, if the prefix is also 'b' (which is the
>> common case) we get the falsely warning:
>>
>> patch prefix 'b' exists, appears to be a -p0 patch
>>
>> So warn only if prefix is not 'b'
>>
>
> The checkpatch script that is maintained here is really only intended
> for its use in the kernel development. You may use checkpatch anywhere
> else, but any changes that increase complexity for those other use
> cases is really difficult to argue for inclusion in the kernel
> repository. The checkpatch script currently is already large and
> complex enough and all rules need to be understood as rough
> heuristics, not as strict rules.
>
> So, can you point to a kernel repository where there is actually a
> file 'b' included? On a quick scan, I could not find a file 'b' in the
> current trees of the repositories on my machine.
>
> I am just letting you know about what I have observed; I do not decide
> on the inclusion of this patch, though.
Hi, a 'b' file might make it to the source folder as an untracked file.
This actually happened to me since I was too lazy to give it a meaningful name.
Then I got this warning and it took me some time to figure out what is the problem.
Thanks,
Dafna
>
> Lukas
>
>> Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
>> ---
>> scripts/checkpatch.pl | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
>> index 1784921c645d..72263b142e39 100755
>> --- a/scripts/checkpatch.pl
>> +++ b/scripts/checkpatch.pl
>> @@ -2821,7 +2821,7 @@ sub process {
>> $in_commit_log = 0;
>>
>> $p1_prefix = $1;
>> - if (!$file && $tree && $p1_prefix ne '' &&
>> + if (!$file && $tree && $p1_prefix ne '' && $p1_prefix ne 'b' &&
>> -e "$root/$p1_prefix") {
>> WARN("PATCH_PREFIX",
>> "patch prefix '$p1_prefix' exists, appears to be a -p0 patch\n");
>
>> --
>> 2.17.1
>>
next prev parent reply other threads:[~2022-01-11 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 20:05 Dafna Hirschfeld
2022-01-11 10:18 ` Lukas Bulwahn
2022-01-11 10:47 ` Dafna Hirschfeld [this message]
2022-01-11 11:27 ` Lukas Bulwahn
2022-01-11 12:06 ` Dafna Hirschfeld
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=ff6e3942-24e4-25ec-946c-cc6301ebf260@collabora.com \
--to=dafna.hirschfeld@collabora.com \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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
all inboxes | Powered by JetHome®