From: Coiby Xu <coxu@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: kexec@lists.infradead.org, x86@kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] x86/crash: Use set_memory_p instead of __set_memory_prot
Date: Wed, 14 Jan 2026 10:36:52 +0800 [thread overview]
Message-ID: <aWcAZbbRQtMn2H2U@Rk> (raw)
In-Reply-To: <20260113142733.GKaWZWVR_0Q_awGa80@fat_crate.local>
On Tue, Jan 13, 2026 at 03:27:33PM +0100, Borislav Petkov wrote:
>On Tue, Jan 13, 2026 at 06:14:38PM +0800, Coiby Xu wrote:
>> I thought smaller patches are easier to review. But seems it's unnecessary
>> for this case.
>
>Right, especially if the two patches do one logical thing - removing
>__set_memory_prot(). Then one patch is better.
I see, thanks for the explanation!
>
>> Thanks for squashing the two commits and also updating the commit
>> message! I notice you also added a Link tag. Does it mean there is no
>> need for me to re-send your new patch as v2?
>
>Yap, I can queue it, no need.
Great, thanks for taking care of the patch!
>
>Thx.
>
>--
>Regards/Gruss,
> Boris.
>
>https://people.kernel.org/tglx/notes-about-netiquette
>
--
Best regards,
Coiby
next prev parent reply other threads:[~2026-01-14 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 9:50 [PATCH 1/2] x86/crash: Use set_memory_p instead of __set_memory_prot Coiby Xu
2026-01-06 9:50 ` [PATCH 2/2] Reapply "x86/mm: Remove unused __set_memory_prot()" Coiby Xu
2026-01-09 20:11 ` [PATCH 1/2] x86/crash: Use set_memory_p instead of __set_memory_prot Borislav Petkov
2026-01-13 10:14 ` Coiby Xu
2026-01-13 14:27 ` Borislav Petkov
2026-01-14 2:36 ` Coiby Xu [this message]
2026-01-13 15:12 ` [tip: x86/cleanups] x86/crash: Use set_memory_p() instead of __set_memory_prot() tip-bot2 for Coiby Xu
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=aWcAZbbRQtMn2H2U@Rk \
--to=coxu@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.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