From: Joe Perches <joe@perches.com>
To: Ian Rogers <irogers@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Kuan-Wei Chiu <visitorckw@gmail.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andy Whitcroft <apw@canonical.com>,
linux-kernel@vger.kernel.org, Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v1] checkpatch: Warn about sign offs if there's an accidental patch separator
Date: Sun, 04 Jan 2026 14:22:10 -0800 [thread overview]
Message-ID: <f9f44e6ef34592d7bc3558d6cf8a00d643bac7c4.camel@perches.com> (raw)
In-Reply-To: <CAP-5=fXqX4QmbAf1vuUhy6b-KmUmYms+8GhJjq2gtiawVkwYvg@mail.gmail.com>
On Sun, 2026-01-04 at 13:13 -0800, Ian Rogers wrote:
> On Sun, Jan 4, 2026 at 10:54 AM Joe Perches <joe@perches.com> wrote:
> >
> > On Mon, 2026-01-05 at 01:37 +0800, Kuan-Wei Chiu wrote:
> > > +Cc Andrew Morton,
> > []
> >
> > > That said, any Ack/Review or feedback from checkpatch.pl
> > > maintainers/reviewers would still be helpful and appreciated.
> >
> >
> > I think most of this is pointless and incorrect besides.
> > A patch separator is specifically 3 dashes not a line that
> > starts with 3 or more dashes.
>
> Thanks Joe, do you have a reference for this?
[]
> > See the original problem
> > https://lore.kernel.org/lkml/20251203214706.112174-7-irogers@google.com/
Did you look at this?
next prev parent reply other threads:[~2026-01-04 22:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 5:34 [PATCH v1] checkpatch: Warn about sign offs if there's an accidental patch separator Ian Rogers
2025-12-05 7:22 ` Kuan-Wei Chiu
2026-01-04 1:10 ` Ian Rogers
2026-01-04 17:37 ` Kuan-Wei Chiu
[not found] ` <195a2cba2b461a0ab99ae004bdf079b038db8b07.camel@perches.com>
2026-01-04 21:13 ` Ian Rogers
2026-01-04 22:22 ` Joe Perches [this message]
2026-01-05 15:39 ` Ian Rogers
2026-01-05 16:46 ` Joe Perches
2026-01-05 17:13 ` Ian Rogers
2026-01-14 3:33 ` Andrew Morton
2026-01-14 5:29 ` Stephen Rothwell
2026-01-14 18:20 ` Joe Perches
2026-01-14 19:01 ` Ian Rogers
2026-01-16 17:42 ` [PATCH] checkpatch: Add an invalid patch separator test Joe Perches
2026-01-16 20:48 ` Andrew Morton
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=f9f44e6ef34592d7bc3558d6cf8a00d643bac7c4.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=namhyung@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=visitorckw@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