From: Joe Perches <joe@perches.com>
To: Masahiro Yamada <masahiroy@kernel.org>,
Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: checkpatch: question about "patch prefix 'b' exists" warning
Date: Sat, 24 Sep 2022 14:43:32 -0700 [thread overview]
Message-ID: <3bd6cce3cb8cb2fef74db8715dbe5170c142c5e6.camel@perches.com> (raw)
In-Reply-To: <CAK7LNASNNm9Fa0eqcayoqnGK+pLEUVMwwL4BANrV+gZMDDta6g@mail.gmail.com>
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@kernel.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.
next prev parent reply other threads:[~2022-09-24 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK7LNAThr6z-bu3znMps0MaS0m-VYxUPv-DPkr-XzWeLJ5Vu4g@mail.gmail.com>
2022-09-24 18:03 ` Masahiro Yamada
2022-09-24 21:43 ` Joe Perches [this message]
2022-09-25 0:54 ` Masahiro Yamada
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=3bd6cce3cb8cb2fef74db8715dbe5170c142c5e6.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=masahiroy@kernel.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
all inboxes | Powered by JetHome®