From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Feng Tang <feng.tang@linux.alibaba.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Nathan Chancellor <nathan@kernel.org>,
Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH v1 1/1] panic: Fix compilation error (`make W=1`)
Date: Fri, 11 Jul 2025 09:01:40 +0300 [thread overview]
Message-ID: <aHCoxOK3WlouqbA_@smile.fi.intel.com> (raw)
In-Reply-To: <aHBgwRrFfmEWcp-T@U-2FWC9VHC-2323.local>
On Fri, Jul 11, 2025 at 08:54:25AM +0800, Feng Tang wrote:
> On Thu, Jul 10, 2025 at 03:01:33PM -0700, Andrew Morton wrote:
> > On Thu, 10 Jul 2025 12:48:16 +0300 Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
...
> > > - char names[sizeof(sys_info_avail) + 1];
> > > + char names[sizeof("tasks,mem,timers,locks,ftrace,all_bt,blocked_tasks") + 1];
> >
> > Yes, that's neater than the fix we currently have. I'll grab, thanks.
>
> sys_info_avail[] has another purpose for being a counterpart of si_names[],
> which could be extended in future, so we make it obviously stand-alone. As
> for definition of si_names[], we explicitly added comment:
>
> /*
> * When 'si_names' gets updated, please make sure the 'sys_info_avail'
> * below is updated accordingly.
> */
> static const struct sys_info_name si_names[] = {
> { SYS_INFO_TASKS, "tasks" },
> { SYS_INFO_MEM, "mem" },
>
> which has also been discussed in another thread:
> https://lore.kernel.org/lkml/aG3o2RFHc5iXnJef@U-2FWC9VHC-2323.local/
Ah, this is interesting. Let's rethink about the solution.
> And I suggest to keep sys_info_avail[], and either Nathan or Sergey's patch
> works for me.
I definitely not suggest to leave build broken
(try with CONFOG_WERROR=y, which is default).
> Sorry for the inconvenience, and I should upgrade my gcc :)
I have compiled with clang-19.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-07-11 6:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 9:48 Andy Shevchenko
[not found] ` <aG-Y2RhcxgrWuq27@U-2FWC9VHC-2323.local>
[not found] ` <aG--Yu57lpHnroCe@smile.fi.intel.com>
2025-07-10 13:24 ` Andy Shevchenko
2025-07-10 22:01 ` Andrew Morton
2025-07-11 0:54 ` Feng Tang
2025-07-11 1:49 ` Nathan Chancellor
2025-07-11 2:48 ` Feng Tang
2025-07-11 6:04 ` Andy Shevchenko
2025-07-11 6:44 ` Andy Shevchenko
2025-07-11 6:01 ` Andy Shevchenko [this message]
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=aHCoxOK3WlouqbA_@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=pmladek@suse.com \
--cc=senozhatsky@chromium.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®