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: Fri, 28 Aug 2026 16:11:30 +0200 [thread overview]
Message-ID: <20260828.ye1xoPeeweel@digikod.net> (raw)
In-Reply-To: <CANiq72nPB9-GpYFpyOxedtFRDGb+6EoGjMCYQ00S6wh6dth4Qg@mail.gmail.com>
Hi Miguel,
Could you please sent the PR to Linus and Cc stable@?
Thanks,
Mickaël
On Wed, Jul 08, 2026 at 02:49:35PM +0200, Miguel Ojeda wrote:
> On Wed, Jul 8, 2026 at 2:34 PM Mickaël Salaün <mic@digikod.net> wrote:
> >
> > I guess parts 2 and 3 should probably be send for v7.13 (it's a big
> > patch) whereas part 1 in 7.12-rcX, so I'll let you handle that properly.
>
> Sometimes I sent these PRs to Linus in -rcs, to catch new code, so it
> should be fine, I can do it either way.
>
> > Yes, thanks. I'll keep the Landlock-specific patch I sent.
>
> Sounds good.
>
> > Yes, but I enforce it for Landlock, which helps a lot:
>
> Yeah, that is very good, and I am very glad to see it is useful for
> you and that you could get to enforcement.
>
> What I meant is that it cannot really be "truly enforced" across
> trees, especially if the config keeps changing and so on; unlike
> `rustfmt`, where one is not supposed to push anything to linux-next
> that doesn't pass.
>
> I mean, I would love if we could, but it is a very long-term thing.
> Over time, my hope is that more subsystems start enforcing it on their
> own and so on.
>
> Cheers,
> Miguel
next prev parent reply other threads:[~2026-08-28 14:11 UTC|newest]
Thread overview: 11+ 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 [this message]
2026-08-30 10:09 ` Miguel Ojeda
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=20260828.ye1xoPeeweel@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®