From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Miguel Ojeda <ojeda@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] clang-format: Update with v6.11-rc1's `for_each` macro list
Date: Mon, 29 Jul 2024 23:39:02 +0200 [thread overview]
Message-ID: <17e81b06-7778-44f4-94cd-6a2b1fe5c7e0@gmail.com> (raw)
In-Reply-To: <CANiq72kFpS5BE7Ea8=Z6SUi_Y2RAt5wsssHyqL3ocgR1UOHJMg@mail.gmail.com>
On 29/07/2024 22:14, Miguel Ojeda wrote:
> Hi Javier,
>
> On Mon, Jul 29, 2024 at 9:56 PM Javier Carrasco
> <javier.carrasco.cruz@gmail.com> wrote:
>>
>> Note that commit 4792f9dd1293 ("clang-format: Update with the latest
>> for_each macro list") added the macro `displayid_iter_for_each`, which
>> is not part of include/ and tools/ (it is defined in
>> drivers/gpu/drm/drm_displayid_internal.h), and the shell fragment used
>> to update the list will drop it. In order to keep the macro on the list,
>> manual intervention will always be required.
>
> Thanks for the patch!
>
> That macro was inside `include/` back then, so now it should be
> removed from the list.
>
> Of course, if we want to include internal headers, that is also an
> option to be discussed, but we should be consistent either way.
>
> Cheers,
> Miguel
A quick test threw 326 extra macros that are defined in internal headers
under drivers/ and arch/. Including internal headers would remove the
need to update the list if a macro is moved from inlcude/ to an internal
header, but the list will need to be updated much more often.
Best regards,
Javier Carrasco
next prev parent reply other threads:[~2024-07-29 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 19:55 [PATCH] clang-format: Update with v6.11-rc1's `for_each` macro list Javier Carrasco
2024-07-29 20:14 ` Miguel Ojeda
2024-07-29 21:39 ` Javier Carrasco [this message]
2024-07-29 21:55 ` Miguel Ojeda
2024-07-29 22:42 ` Javier Carrasco
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=17e81b06-7778-44f4-94cd-6a2b1fe5c7e0@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox