From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: Johannes Berg <johannes@sipsolutions.net>, linux-kernel@vger.kernel.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Berg <johannes.berg@intel.com>,
Benjamin Berg <benjamin.berg@intel.com>
Subject: Re: [PATCH] scripts: gdb: move MNT_* constants to gdb-parsed
Date: Wed, 18 Jun 2025 14:06:23 -0700 [thread overview]
Message-ID: <a01d8c8e-21b7-488d-8fa2-0a8710bc1e9a@oracle.com> (raw)
In-Reply-To: <20250618134629.25700-2-johannes@sipsolutions.net>
On 6/18/25 06:46, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Since these are now no longer defines, but in an enum.
>
> Fixes: 101f2bbab541 ("fs: convert mount flags to enum")
> Reviewed-by: Benjamin Berg <benjamin.berg@intel.com>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
The exact same change was already submitted and discussed here:
https://lore.kernel.org/all/20250601055027.3661480-1-tony.ambardar@gmail.com/
I don't know what tree this would go through, so I can't tell whether it
was picked up or not. But I think there's consensus that it's a good
fix, and several folks have written or reviewed the change.
Thanks,
Stephen
> ---
> scripts/gdb/linux/constants.py.in | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/scripts/gdb/linux/constants.py.in b/scripts/gdb/linux/constants.py.in
> index fd6bd69c5096..d5e3069f42a7 100644
> --- a/scripts/gdb/linux/constants.py.in
> +++ b/scripts/gdb/linux/constants.py.in
> @@ -73,12 +73,12 @@ if IS_BUILTIN(CONFIG_MODULES):
> LX_GDBPARSED(MOD_RO_AFTER_INIT)
>
> /* linux/mount.h */
> -LX_VALUE(MNT_NOSUID)
> -LX_VALUE(MNT_NODEV)
> -LX_VALUE(MNT_NOEXEC)
> -LX_VALUE(MNT_NOATIME)
> -LX_VALUE(MNT_NODIRATIME)
> -LX_VALUE(MNT_RELATIME)
> +LX_GDBPARSED(MNT_NOSUID)
> +LX_GDBPARSED(MNT_NODEV)
> +LX_GDBPARSED(MNT_NOEXEC)
> +LX_GDBPARSED(MNT_NOATIME)
> +LX_GDBPARSED(MNT_NODIRATIME)
> +LX_GDBPARSED(MNT_RELATIME)
>
> /* linux/threads.h */
> LX_VALUE(NR_CPUS)
next prev parent reply other threads:[~2025-06-18 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 13:46 Johannes Berg
2025-06-18 21:06 ` Stephen Brennan [this message]
2025-06-18 21:08 ` Johannes Berg
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=a01d8c8e-21b7-488d-8fa2-0a8710bc1e9a@oracle.com \
--to=stephen.s.brennan@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=benjamin.berg@intel.com \
--cc=jan.kiszka@siemens.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®