From: Jani Nikula <jani.nikula@intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Hendrik Hamerlinck <hendrik.hamerlinck@hammernet.be>,
dwaipayanray1@gmail.com, lukas.bulwahn@gmail.com,
joe@perches.com, corbet@lwn.net, apw@canonical.com,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH] checkpatch: validate commit tag ordering
Date: Fri, 01 Aug 2025 10:55:55 +0300 [thread overview]
Message-ID: <3e9106d35d41a044adeadffeea32fa096c9e1370@intel.com> (raw)
In-Reply-To: <45f0995f-17ac-45a3-8bc0-3b276ee91a9d@kernel.org>
On Thu, 31 Jul 2025, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> On 31/07/2025 13:55, Geert Uytterhoeven wrote:
>> B4 does not follow the proper order:
>
> There is no "proper order" in terms of absolute facts.
Let's just decide whatever order b4 uses *is* the proper order, and save
ourselves endless hours of debating! :p
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-08-01 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 7:20 [PATCH] checkpatch: validate commit tag ordering Hendrik Hamerlinck
2025-07-24 15:04 ` Akira Yokosawa
2025-07-24 19:10 ` Jeff Johnson
2025-07-24 19:43 ` Konstantin Ryabitsev
2025-07-25 8:42 ` Krzysztof Kozlowski
2025-07-31 11:55 ` Geert Uytterhoeven
2025-07-31 12:46 ` Krzysztof Kozlowski
2025-08-01 7:55 ` Jani Nikula [this message]
2025-08-02 10:12 ` Mauro Carvalho Chehab
2025-08-02 16:26 ` Konstantin Ryabitsev
2025-07-26 7:34 ` Hendrik Hamerlinck
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=3e9106d35d41a044adeadffeea32fa096c9e1370@intel.com \
--to=jani.nikula@intel.com \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=geert@linux-m68k.org \
--cc=hendrik.hamerlinck@hammernet.be \
--cc=joe@perches.com \
--cc=konstantin@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.