From: Borislav Petkov <bp@alien8.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
Yazen Ghannam <Yazen.Ghannam@amd.com>,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH v1 1/1] RAS/AMD/ATL: Drop malformed default N from Kconfig
Date: Wed, 13 May 2026 19:02:40 +0200 [thread overview]
Message-ID: <20260513170240.GHagSusHdkGcYLS8v1@fat_crate.local> (raw)
In-Reply-To: <agSnXBBS_ur1YEYQ@ashevche-desk.local>
On Wed, May 13, 2026 at 07:31:24PM +0300, Andy Shevchenko wrote:
> On Wed, May 13, 2026 at 06:27:44PM +0200, Borislav Petkov wrote:
> > On Wed, May 13, 2026 at 06:22:53PM +0200, Andy Shevchenko wrote:
> > > First of all, it has to be 'default n' (small letter n), otherwise
> > > it looks for CONFIG_N which is absent and in case of appearance
>
> > Who does look for CONFIG_N?
>
> Hmm... I need to rephrase that. Any suggestion how to refer to the Kconfig
> symbol in a clearer way?
So I tried searching for CONFIG_N in "make menuconfig" and it gave me many
results, but with or without your patch I didn't see a difference.
Just point to the "default" grammar definition - I see
config NEW_NAME
bool "New option name"
default OLD_NAME
in Documentation/kbuild/kconfig-language.rst which says that default <symbols
in caps> refers to a symbol but the grammar should be properly documented
somewhere too (can't find it now...).
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-05-13 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 16:22 [PATCH v1 1/1] RAS/AMD/ATL: Drop malformed default N from Kconfig Andy Shevchenko
2026-05-13 16:27 ` Borislav Petkov
2026-05-13 16:31 ` Andy Shevchenko
2026-05-13 17:02 ` Borislav Petkov [this message]
2026-05-13 17:19 ` Andy Shevchenko
2026-05-13 18:04 ` Borislav Petkov
2026-05-13 20:30 ` 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=20260513170240.GHagSusHdkGcYLS8v1@fat_crate.local \
--to=bp@alien8.de \
--cc=Yazen.Ghannam@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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