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: Wed, 8 Jul 2026 13:20:38 +0200 [thread overview]
Message-ID: <20260708.kae9Abuath6i@digikod.net> (raw)
In-Reply-To: <CANiq72kgYwB0CXizay_5ejvqzcxxV235sm=xEwBNTGpqGcdUnA@mail.gmail.com>
On Wed, Jul 08, 2026 at 01:11:31PM +0200, Miguel Ojeda wrote:
> On Wed, Jul 8, 2026 at 1:10 PM Mickaël Salaün <mic@digikod.net> wrote:
> >
> > What do you mean? Running clang-format -i security/landlock/*.[ch] does
> > some changes.
>
> I mean the command on the `.clang-format` file:
>
> # Taken from:
> # git grep -h '^#define [^[:space:]]*for_each[^[:space:]]*('
> include/ tools/ \
> # | sed "s,^#define \([^[:space:]]*for_each[^[:space:]]*\)(.*$, - '\1'," \
> # | LC_ALL=C sort -u
Ok, so the guard/scoped_guard changes will disappear once you refreshed
the .clang-format file. This means that I should not apply the Landlock
changes [1] right?
[1] https://lore.kernel.org/all/20260708110635.2083515-1-mic@digikod.net/
Do you plan to send this file update with a following v7.2-rc?
>
> Cheers,
> Miguel
next prev parent reply other threads:[~2026-07-08 11:30 UTC|newest]
Thread overview: 9+ 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 [this message]
2026-07-08 11:31 ` Miguel Ojeda
2026-07-08 12:34 ` Mickaël Salaün
2026-07-08 12:49 ` 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=20260708.kae9Abuath6i@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
Powered by JetHome