From: Ingo Molnar <mingo@kernel.org>
To: Nikolay Borisov <nik.borisov@suse.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/alternatives: Make smp_text_poke_batch_process subsume smp_text_poke_batch_finish
Date: Fri, 4 Apr 2025 11:55:40 +0200 [thread overview]
Message-ID: <Z--snCDhK2u_m4lP@gmail.com> (raw)
In-Reply-To: <20250403153956.1913607-1-nik.borisov@suse.com>
* Nikolay Borisov <nik.borisov@suse.com> wrote:
> Simplify the alternatives interface some more by moving the
> poke_batch_finish check into poke_batch_process and renaming the latter.
> The net effect is one less function name to consider when reading the
> code.
>
> Signed-off-by: Nikolay Borisov <nik.borisov@suse.com>
> ---
> arch/x86/kernel/alternative.c | 20 +++++++++-----------
> 1 file changed, 9 insertions(+), 11 deletions(-)
Applied, thanks!
Ingo
prev parent reply other threads:[~2025-04-04 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 15:39 [PATCH] x86/alternatives: Make smp_text_poke_batch_process subsume smp_text_poke_batch_finish Nikolay Borisov
2025-04-04 9:55 ` Ingo Molnar [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=Z--snCDhK2u_m4lP@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).