From: Nathan Chancellor <nathan@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Andreas Schwab" <schwab@linux-m68k.org>,
"Nicolas Schier" <nicolas.schier@linux.dev>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
linux-kbuild@vger.kernel.org, linux-m68k@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] kbuild: uapi: Strip comments before size type check
Date: Mon, 6 Oct 2025 11:02:01 -0700 [thread overview]
Message-ID: <20251006180201.GA429708@ax162> (raw)
In-Reply-To: <CAMuHMdXdeJ6Bq=zA7QcN82YNaZW3R8ebeXpGzqHus-KPkSj5XA@mail.gmail.com>
Hi Geert,
On Mon, Oct 06, 2025 at 03:20:52PM +0200, Geert Uytterhoeven wrote:
> On Mon, 6 Oct 2025 at 14:40, Andreas Schwab <schwab@linux-m68k.org> wrote:
> > On Okt 06 2025, Geert Uytterhoeven wrote:
> > > --- a/usr/include/headers_check.pl
> > > +++ b/usr/include/headers_check.pl
> > > @@ -155,6 +155,8 @@ sub check_sizetypes
> > > if (my $included = ($line =~ /^\s*#\s*include\s+[<"](\S+)[>"]/)[0]) {
> > > check_include_typesh($included);
> > > }
> > > + # strip comments (single-line only)
> > > + $line =~ s@\/\*.*?\*\/@@;
> >
> > I don't think you need to quote the forward slashes in the regexp.
>
> Thanks, you are right!
>
> So far for not just following my instinct, but looking for similar functionality
> in other scripts like scripts/kernel-doc.pl...
I will fix this up when applying. I think I am going to adjust the
comment to
# strip single-line comments, as types may be referenced within them
just to be a little more verbose about why it is being done.
Sorry for the breakage!
Cheers,
Nathan
next prev parent reply other threads:[~2025-10-06 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 12:33 [PATCH v2] kbuild: uapi: Strip comments before size type check Geert Uytterhoeven
2025-10-06 12:40 ` Andreas Schwab
2025-10-06 13:20 ` Geert Uytterhoeven
2025-10-06 18:02 ` Nathan Chancellor [this message]
2025-10-07 7:42 ` Geert Uytterhoeven
2025-10-07 16:55 ` Nathan Chancellor
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=20251006180201.GA429708@ax162 \
--to=nathan@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=schwab@linux-m68k.org \
--cc=thomas.weissschuh@linutronix.de \
/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