From: Feng Tang <feng.tang@linux.alibaba.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH v2 2/6] panic: sys_info: Align constant definition names with parameters
Date: Thu, 30 Oct 2025 09:59:35 +0800 [thread overview]
Message-ID: <aQLGhzh9UOYNM-V7@U-2FWC9VHC-2323.local> (raw)
In-Reply-To: <20251029111202.3217870-4-andriy.shevchenko@linux.intel.com>
On Wed, Oct 29, 2025 at 12:07:37PM +0100, Andy Shevchenko wrote:
> Align constant definition names with parameters to make it easier
> to map. It's also better to maintain and extend the names while
> keeping their uniqueness.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: Feng Tang <feng.tang@linux.alibaba.com>
Thanks,
Feng
>
> ---
> include/linux/sys_info.h | 2 +-
> kernel/panic.c | 2 +-
> lib/sys_info.c | 4 ++--
> 3 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/sys_info.h b/include/linux/sys_info.h
> index 89d77dc4f2ed..a5bc3ea3d44b 100644
> --- a/include/linux/sys_info.h
> +++ b/include/linux/sys_info.h
> @@ -14,7 +14,7 @@
> #define SYS_INFO_LOCKS 0x00000008
> #define SYS_INFO_FTRACE 0x00000010
> #define SYS_INFO_PANIC_CONSOLE_REPLAY 0x00000020
> -#define SYS_INFO_ALL_CPU_BT 0x00000040
> +#define SYS_INFO_ALL_BT 0x00000040
> #define SYS_INFO_BLOCKED_TASKS 0x00000080
>
> void sys_info(unsigned long si_mask);
> diff --git a/kernel/panic.c b/kernel/panic.c
> index 341c66948dcb..0d52210a9e2b 100644
> --- a/kernel/panic.c
> +++ b/kernel/panic.c
> @@ -401,7 +401,7 @@ static void panic_trigger_all_cpu_backtrace(void)
> */
> static void panic_other_cpus_shutdown(bool crash_kexec)
> {
> - if (panic_print & SYS_INFO_ALL_CPU_BT)
> + if (panic_print & SYS_INFO_ALL_BT)
> panic_trigger_all_cpu_backtrace();
>
> /*
> diff --git a/lib/sys_info.c b/lib/sys_info.c
> index d542a024406a..6b0188b30227 100644
> --- a/lib/sys_info.c
> +++ b/lib/sys_info.c
> @@ -23,7 +23,7 @@ static const struct sys_info_name si_names[] = {
> { SYS_INFO_TIMERS, "timers" },
> { SYS_INFO_LOCKS, "locks" },
> { SYS_INFO_FTRACE, "ftrace" },
> - { SYS_INFO_ALL_CPU_BT, "all_bt" },
> + { SYS_INFO_ALL_BT, "all_bt" },
> { SYS_INFO_BLOCKED_TASKS, "blocked_tasks" },
> };
>
> @@ -118,7 +118,7 @@ void sys_info(unsigned long si_mask)
> if (si_mask & SYS_INFO_FTRACE)
> ftrace_dump(DUMP_ALL);
>
> - if (si_mask & SYS_INFO_ALL_CPU_BT)
> + if (si_mask & SYS_INFO_ALL_BT)
> trigger_all_cpu_backtrace();
>
> if (si_mask & SYS_INFO_BLOCKED_TASKS)
> --
> 2.50.1
next prev parent reply other threads:[~2025-10-30 1:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 11:07 [PATCH v2 0/6] panic: sys_info: Refactor and fix a potential issue Andy Shevchenko
2025-10-29 11:07 ` [PATCH v2 1/6] panic: sys_info: Capture si_bits_global before iterating over it Andy Shevchenko
2025-10-30 2:00 ` Feng Tang
2025-10-29 11:07 ` [PATCH v2 2/6] panic: sys_info: Align constant definition names with parameters Andy Shevchenko
2025-10-30 1:59 ` Feng Tang [this message]
2025-10-29 11:07 ` [PATCH v2 3/6] panic: sys_info: Replace struct sys_info_name with plain array of strings Andy Shevchenko
2025-10-30 2:01 ` Feng Tang
2025-10-30 7:36 ` Andy Shevchenko
2025-10-30 8:45 ` Feng Tang
2025-10-30 9:05 ` Andy Shevchenko
2025-10-30 10:36 ` Feng Tang
2025-10-29 11:07 ` [PATCH v2 4/6] panic: sys_info: Rewrite a fix for a compilation error (`make W=1`) Andy Shevchenko
2025-10-29 11:07 ` [PATCH v2 5/6] panic: sys_info: Deduplicate local variable 'table; assignments Andy Shevchenko
2025-10-30 2:11 ` Feng Tang
2025-10-29 11:07 ` [PATCH v2 6/6] panic: sys_info: Factor out read and write handlers Andy Shevchenko
2025-10-30 2:06 ` Feng Tang
2025-10-30 7:44 ` Andy Shevchenko
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=aQLGhzh9UOYNM-V7@U-2FWC9VHC-2323.local \
--to=feng.tang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.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 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®