The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: make config X86_FEATURE_NAMES visible with EXPERT
Date: Tue, 9 May 2023 07:07:15 -0700	[thread overview]
Message-ID: <7cbe80f0-dcc3-bfc3-3bd8-c9f96704618d@intel.com> (raw)
In-Reply-To: <20230509084007.24373-1-lukas.bulwahn@gmail.com>

On 5/9/23 01:40, Lukas Bulwahn wrote:
> Commit 6a108a14fa35 ("kconfig: rename CONFIG_EMBEDDED to CONFIG_EXPERT")
> introduces CONFIG_EXPERT to carry the previous intent of CONFIG_EMBEDDED
> and just gives that intent a much better name.

That was quite the changelog, and I'm still not quite sure:

What is the problem with the existing code?

What is the end user visible impact of this problem and of this proposed
change?



  reply	other threads:[~2023-05-09 14:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09  8:40 [PATCH] x86: make config X86_FEATURE_NAMES visible with EXPERT Lukas Bulwahn
2023-05-09 14:07 ` Dave Hansen [this message]
2023-05-09 18:20   ` Lukas Bulwahn
2023-05-09 18:38     ` Dave Hansen
2023-05-09 18:41       ` Borislav Petkov
2023-05-09 18:43         ` Dave Hansen
2023-05-09 19:03           ` Borislav Petkov
2023-05-10  7:01             ` Lukas Bulwahn
2023-05-10  7:46       ` Lukas Bulwahn
2023-05-10  1:07 ` H. Peter Anvin
2023-05-10  7:51   ` Lukas Bulwahn

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=7cbe80f0-dcc3-bfc3-3bd8-c9f96704618d@intel.com \
    --to=dave.hansen@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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