[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK7LNAS_06Ry=eF_9Ahiky=75f5uuqEod990prGxEo1kkNgBRA@mail.gmail.com>
Date: Sun, 25 Sep 2022 09:54:36 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Joe Perches <joe@...ches.com>
Cc: Andy Whitcroft <apw@...onical.com>,
Dwaipayan Ray <dwaipayanray1@...il.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: checkpatch: question about "patch prefix 'b' exists" warning
On Sun, Sep 25, 2022 at 6:43 AM Joe Perches <joe@...ches.com> wrote:
>
> On Sun, 2022-09-25 at 03:03 +0900, Masahiro Yamada wrote:
> > (+CC: LKML)
> > On Sun, Sep 25, 2022 at 3:00 AM Masahiro Yamada <masahiroy@...nel.org> wrote:
> > > When I used scripts/checkpatch.pl to check a patch file
> > > generated by 'git format-patch', I observed this warning,
> > >
> > > WARNING: patch prefix 'b' exists, appears to be a -p0 patch
> []
> > > Is this intentional behavior?
>
> Yes.
>
But, my patch is apparently -p1 patch.
Everyone knows "git format-patch" uses a/ and b/ prefixes.
Can we handle 'b' as a special case?
Or, can we warn it only when $root/$p1_prefix is a directory, at least?
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists