From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Feng Tang <feng.tang@linux.alibaba.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.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:44:41 +0300 [thread overview]
Message-ID: <aHCy2Tv0zmhklKdo@smile.fi.intel.com> (raw)
In-Reply-To: <aHCpbB7cfwfdFBzl@smile.fi.intel.com>
On Fri, Jul 11, 2025 at 09:04:29AM +0300, Andy Shevchenko wrote:
> On Fri, Jul 11, 2025 at 10:48:29AM +0800, Feng Tang wrote:
> > On Thu, Jul 10, 2025 at 06:49:47PM -0700, Nathan Chancellor wrote:
...
> > We can even move the SYS_INFO_MAX_LEN definition close to si_names[],
>
> Agree.
>
> > initially sys_info_avail[] was next to si_names[], and was moved inside
> > "#ifdef CONFIG_SYSCTL" region for compiling CONFIG_SYSCTL=n case.
>
> But let me think a bit, perhaps we can come up with something even better.
Okay, guys, I have a better approach found. Let me mock up a patch series
for that (we need one prerequisite).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-07-11 6:44 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 [this message]
2025-07-11 6:01 ` 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=aHCy2Tv0zmhklKdo@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®