From: Dave Hansen <dave.hansen@intel.com>
To: "Ionut Nechita (Wind River)" <ionut.nechita@windriver.com>,
x86@kernel.org, kexec@lists.infradead.org
Cc: tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com,
akpm@linux-foundation.org, baoquan.he@linux.dev, rppt@kernel.org,
pasha.tatashin@soleen.com, pratyush@kernel.org,
ruirui.yang@linux.dev, eric.devolder@oracle.com,
hbathini@linux.ibm.com, sourabhjain@linux.ibm.com,
ruanjinjie@huawei.com, brads@mainlining.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] x86/crash: reserve elfcorehdr for CONFIG_NR_CPUS, not CONFIG_NR_CPUS_DEFAULT
Date: Wed, 2 Sep 2026 14:24:16 -0700 [thread overview]
Message-ID: <97887aeb-4454-4cb9-91ad-d0477d3ea5dd@intel.com> (raw)
In-Reply-To: <20260901071041.16311-2-ionut.nechita@windriver.com>
On 9/1/26 00:10, Ionut Nechita (Wind River) wrote:
> Assisted-by: LLM
This seems a _bit_ opaque and imprecise. Could you take a quick look
through:
https://docs.kernel.org/process/generated-content.html
and try to err a bit more on the side of transparency for the next one?
next prev parent reply other threads:[~2026-09-02 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 7:10 [PATCH v5 0/2] x86/crash: size the elfcorehdr reservation with NR_CPUS Ionut Nechita (Wind River)
2026-09-01 7:10 ` [PATCH v5 1/2] x86/crash: reserve elfcorehdr for CONFIG_NR_CPUS, not CONFIG_NR_CPUS_DEFAULT Ionut Nechita (Wind River)
2026-09-02 6:21 ` Sourabh Jain
2026-09-02 21:24 ` Dave Hansen [this message]
2026-09-02 21:27 ` Bradley Morgan
2026-09-02 21:34 ` Dave Hansen
2026-09-02 21:38 ` Bradley Morgan
2026-09-01 7:10 ` [PATCH v5 2/2] crash: update stale NR_CPUS_DEFAULT references in elfcorehdr sizing docs Ionut Nechita (Wind River)
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=97887aeb-4454-4cb9-91ad-d0477d3ea5dd@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=bp@alien8.de \
--cc=brads@mainlining.org \
--cc=dave.hansen@linux.intel.com \
--cc=eric.devolder@oracle.com \
--cc=hbathini@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=ionut.nechita@windriver.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=ruirui.yang@linux.dev \
--cc=sourabhjain@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.