From: "Mickaël Salaün" <mic@digikod.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
linux-kernel@vger.kernel.org,
"Nathan Chancellor" <nathan@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Bart Van Assche" <bvanassche@acm.org>,
"Günther Noack" <gnoack@google.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>
Subject: Re: [PATCH v1] clang-format: Fix formatting of guard()
Date: Thu, 3 Sep 2026 19:31:19 +0200 [thread overview]
Message-ID: <20260903.eisiequ7Mo2A@digikod.net> (raw)
In-Reply-To: <CANiq72=iYpz4ZkPGPfPZKQvsdpPo1f7KgzUL59VzcrN_6A2W3Q@mail.gmail.com>
On Sun, Aug 30, 2026 at 12:09:18PM +0200, Miguel Ojeda wrote:
> On Fri, Aug 28, 2026 at 4:11 PM Mickaël Salaün <mic@digikod.net> wrote:
> >
> > Could you please sent the PR to Linus and Cc stable@?
>
> Yeah, sorry, I will prepare the update on top of -rc1.
>
> Regarding the Cc stable, I am not sure. The formatting is not globally
> enforced and such a change could break things for others that may be
> locally enforcing it using whatever list was there in the past.
Well, the bug which is fixed by this patch does "break" the local
enforcement for Landlock code. This is how I found it and why I
reported it.
>
> (Some may even consider the Fixes: tag itself here a stretch depending
> on how one defines "bug"...)
>
> Cheers,
> Miguel
next prev parent reply other threads:[~2026-09-03 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 10:57 Mickaël Salaün
2026-07-08 11:06 ` Miguel Ojeda
2026-07-08 11:10 ` Mickaël Salaün
2026-07-08 11:11 ` Miguel Ojeda
2026-07-08 11:20 ` Mickaël Salaün
2026-07-08 11:31 ` Miguel Ojeda
2026-07-08 12:34 ` Mickaël Salaün
2026-07-08 12:49 ` Miguel Ojeda
2026-08-28 14:11 ` Mickaël Salaün
2026-08-30 10:09 ` Miguel Ojeda
2026-09-03 17:31 ` Mickaël Salaün [this message]
2026-07-08 15:48 ` Bart Van Assche
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=20260903.eisiequ7Mo2A@digikod.net \
--to=mic@digikod.net \
--cc=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=gnoack@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@kernel.org \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.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®