Linux IIO development
 help / color / mirror / Atom feed
From: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
To: david@ixit.cz, 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>,
	Kees Cook <kees@kernel.org>, Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH v3 0/7] x86: Kconfig cleanups and help text improvements
Date: Sat, 22 Mar 2025 16:13:23 +0100	[thread overview]
Message-ID: <5642f2cb-ce34-4474-bb32-50f028a007ad@o2.pl> (raw)
In-Reply-To: <20250321-x86_x2apic-v3-0-b0cbaa6fa338@ixit.cz>

W dniu 21.03.2025 o 21:48, David Heidelberg via B4 Relay pisze:
> I'm resending this mainly because of the first patch, but I find
> all other patches worthy too, so here is the rebased bulk.
>
>   - David

Hello,

Well, thank you for taking care of this. I have quite a lot of unfinished
projects and not so much time for kernel dev now. I'd also like to apologise
for not having responded to your latest e-mail.

Greetings,

Mateusz

> ====
>
> Hello,
>
> There are some problems with Kconfig help texts in the kernel. They are
> frequently confusing and use language that is difficult to understand
> for people unfamiliar with the feature. Sometimes, the help text was not
> updated after important kernel or ecosystem changes. References to
> something "future" or "old" are also usually given without specifying
> any dates.
>
> First version of this patch series was sent out in February 2022.
>
> Greetings,
> Mateusz
>
> Signed-off-by: Mateusz Jończyk <mat.jonczyk@o2.pl>
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
> Changes in v3:
> - Rebased against latest next-20250321.
> - Dropped deprecated patches:
>     2/10  "x86/apic: fix panic message when x2APIC is not supported"
>     4/10  "x86/Kconfig: drop X86_32_NON_STANDARD"
> - Dropped patch I was not very sure about, as there are other refs:
>     10/10 "x86/Kconfig: remove CONFIG_ISA_BUS"
> - Link to v2: https://lore.kernel.org/r/20220911084711.13694-1-mat.jonczyk@o2.pl
>
> ---
> Mateusz Jończyk (7):
>        x86/Kconfig: Enable X86_X2APIC by default and improve help text
>        x86/Kconfig: Always enable ARCH_SPARSEMEM_ENABLE
>        x86/Kconfig: Move all X86_EXTENDED_PLATFORM options together
>        x86/Kconfig: Update lists in X86_EXTENDED_PLATFORM
>        x86/Kconfig: Document CONFIG_PCI_MMCONFIG
>        x86/Kconfig: Make CONFIG_PCI_CNB20LE_QUIRK depend on X86_32
>        x86/Kconfig: Document release year of glibc 2.3.3
>
>   arch/x86/Kconfig | 85 ++++++++++++++++++++++++++++++++++++++------------------
>   1 file changed, 58 insertions(+), 27 deletions(-)
> ---
> base-commit: 9388ec571cb1adba59d1cded2300eeb11827679c
> change-id: 20250320-x86_x2apic-7e92d0f4c47d
>
> Best regards,

      parent reply	other threads:[~2025-03-22 15:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21 20:48 [PATCH v3 0/7] x86: Kconfig cleanups and help text improvements David Heidelberg via B4 Relay
2025-03-21 20:48 ` [PATCH v3 1/7] x86/Kconfig: Enable X86_X2APIC by default and improve help text David Heidelberg via B4 Relay
2025-03-21 20:48 ` [PATCH v3 2/7] x86/Kconfig: Always enable ARCH_SPARSEMEM_ENABLE David Heidelberg via B4 Relay
2025-03-21 20:48 ` [PATCH v3 3/7] x86/Kconfig: Move all X86_EXTENDED_PLATFORM options together David Heidelberg via B4 Relay
2025-03-21 20:48 ` [PATCH v3 4/7] x86/Kconfig: Update lists in X86_EXTENDED_PLATFORM David Heidelberg via B4 Relay
2025-03-21 20:48 ` [PATCH v3 5/7] x86/Kconfig: Document CONFIG_PCI_MMCONFIG David Heidelberg via B4 Relay
2025-03-22  7:11   ` Ingo Molnar
2025-03-21 20:48 ` [PATCH v3 6/7] x86/Kconfig: Make CONFIG_PCI_CNB20LE_QUIRK depend on X86_32 David Heidelberg via B4 Relay
2025-03-21 20:48 ` [PATCH v3 7/7] x86/Kconfig: Document release year of glibc 2.3.3 David Heidelberg via B4 Relay
2025-03-22  7:28   ` Ingo Molnar
2025-03-22 15:13 ` Mateusz Jończyk [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=5642f2cb-ce34-4474-bb32-50f028a007ad@o2.pl \
    --to=mat.jonczyk@o2.pl \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=david@ixit.cz \
    --cc=hpa@zytor.com \
    --cc=jic23@kernel.org \
    --cc=kees@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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