The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Thomas Gleixner <tglx@kernel.org>, 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>,
	Ard Biesheuvel <ardb@kernel.org>,
	"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	"Pratyush Yadav (Google)" <pratyush@kernel.org>,
	Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
	Breno Leitao <leitao@debian.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86: Use IS_ENABLED() for built-in-or-module checks
Date: Tue, 4 Aug 2026 19:43:31 +0200	[thread overview]
Message-ID: <anIkwxhF40qE6_L5@gmail.com> (raw)
In-Reply-To: <20260804115227.62158-4-thorsten.blum@linux.dev>


* Thorsten Blum <thorsten.blum@linux.dev> wrote:

> Replace open-coded built-in-or-module checks for CONFIG_APM, CONFIG_EDD,
> and CONFIG_X86_SPEEDSTEP_SMI with IS_ENABLED().

Please include the phrase "No change in functionality intended." or so
in the changelog, when there's no side effect expected.

Thanks,

	Ingo

  parent reply	other threads:[~2026-08-04 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 11:52 [PATCH 1/2] x86: Use IS_ENABLED() for built-in-or-module checks Thorsten Blum
2026-08-04 11:52 ` [PATCH 2/2] x86/boot: Use bool and IS_ENABLED() in query_edd() Thorsten Blum
2026-08-04 17:58   ` [tip: x86/boot] x86/boot: Use bool and IS_ENABLED() to simplify query_edd() tip-bot2 for Thorsten Blum
2026-08-04 17:43 ` Ingo Molnar [this message]
2026-08-04 17:58 ` [tip: x86/boot] x86/boot: Use IS_ENABLED() to simplify built-in-or-module checks tip-bot2 for Thorsten Blum

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=anIkwxhF40qE6_L5@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=hpa@zytor.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pratyush@kernel.org \
    --cc=rppt@kernel.org \
    --cc=tglx@kernel.org \
    --cc=thorsten.blum@linux.dev \
    --cc=tzimmermann@suse.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