From: Ingo Molnar <mingo@kernel.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: linux-kernel@vger.kernel.org, Paul Menzel <pmenzel@molgen.mpg.de>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] genksyms: Handle typeof_unqual keyword and __seg_{fs,gs} qualifiers
Date: Mon, 14 Apr 2025 09:20:24 +0200 [thread overview]
Message-ID: <Z_y3OIQECdVo6YJL@gmail.com> (raw)
In-Reply-To: <20250413220749.270704-1-ubizjak@gmail.com>
* Uros Bizjak <ubizjak@gmail.com> wrote:
> Handle typeof_unqual, __typeof_unqual and __typeof_unqual__ keywords
> using TYPEOF_KEYW token in the same way as typeof keyword.
>
> Also ignore x86 __seg_fs and __seg_gs named address space qualifiers
> using X86_SEG_KEYW token in the same way as const, volatile or
> restrict qualifiers.
>
> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> Reported-by: Paul Menzel <pmenzel@molgen.mpg.de>
> Closes: https://lore.kernel.org/lkml/81a25a60-de78-43fb-b56a-131151e1c035@molgen.mpg.de/
> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Borislav Petkov <bp@alien8.de>
> ---
> scripts/genksyms/keywords.c | 7 +++++++
> scripts/genksyms/parse.y | 5 ++++-
> 2 files changed, 11 insertions(+), 1 deletion(-)
Thanks, applied to tip:core/urgent.
I've also added this tag for context:
Fixes: ac053946f5c4 ("compiler.h: introduce TYPEOF_UNQUAL() macro")
Ingo
next prev parent reply other threads:[~2025-04-14 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-13 22:07 [PATCH] genksyms: Handle typeof_unqual keyword and __seg_{fs,gs} qualifiers Uros Bizjak
2025-04-14 7:20 ` Ingo Molnar [this message]
2025-04-14 7:52 ` Uros Bizjak
2025-04-14 7:57 ` Ingo Molnar
2025-04-14 7:32 ` [tip: core/urgent] " tip-bot2 for Uros Bizjak
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=Z_y3OIQECdVo6YJL@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=ubizjak@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.