From: Julian Braha <julianbraha@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/cpu: cleanup duplicate dependencies in Kconfig
Date: Tue, 2 Jun 2026 05:33:18 +0100 [thread overview]
Message-ID: <da8d1066-89bc-41ed-9453-086c3e20dc9b@gmail.com> (raw)
In-Reply-To: <ahvdnEFffkxyILPJ@gmail.com>
On 5/31/26 08:05, Ingo Molnar wrote:
> in practice it's useful to see 'at a glance' whether such a
> CPU config option is 32-bit only, 64-bit only or generic.
Hi Ingo,
What do you think about using comments for this? Having spent
quite a bit of time looking at Kconfig, I think that comments
are underused.
- Julian Braha
prev parent reply other threads:[~2026-06-02 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 6:57 Julian Braha
2026-05-31 7:05 ` Ingo Molnar
2026-06-02 4:33 ` Julian Braha [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=da8d1066-89bc-41ed-9453-086c3e20dc9b@gmail.com \
--to=julianbraha@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--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
all inboxes | Powered by JetHome®