From: Catalin Marinas <catalin.marinas@arm.com>
To: Song Liu <song@kernel.org>
Cc: Will Deacon <will@kernel.org>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jpoimboe@kernel.org,
jikos@kernel.org, mbenes@suse.cz, pmladek@suse.com,
joe.lawrence@redhat.com, dylanbhatch@google.com,
fj6611ie@aa.jp.fujitsu.com, mark.rutland@arm.com,
kernel-team@meta.com, Suraj Jitindar Singh <surajjs@amazon.com>,
Torsten Duwe <duwe@suse.de>, Breno Leitao <leitao@debian.org>,
Andrea della Porta <andrea.porta@suse.com>
Subject: Re: [PATCH v4] arm64: Implement HAVE_LIVEPATCH
Date: Mon, 30 Jun 2025 18:16:47 +0100 [thread overview]
Message-ID: <aGLGf5feF4gT-dgR@arm.com> (raw)
In-Reply-To: <CAPhsuW7WY54jYDBtApRRw4mnjM0cZu4GBUZQ58ZHAV+zd79uXw@mail.gmail.com>
On Thu, Jun 26, 2025 at 07:55:28AM -0700, Song Liu wrote:
> On Thu, Jun 26, 2025 at 6:21 AM Will Deacon <will@kernel.org> wrote:
> > On Tue, Jun 17, 2025 at 10:37:34AM -0700, Song Liu wrote:
> > > This is largely based on [1] by Suraj Jitindar Singh.
> >
> > I think it would be useful to preserve at least some parts of the
> > original commit message here so that folks don't have to pull it out
> > of the list archives if they want to see more about the rationale.
>
> The relevant message from the original commit message is:
>
> Allocate a task flag used to represent the patch pending state for the
> task.
>
> Shall I respin this patch to add this? Or maybe Catalin can add
> this while applying the patch?
Please repost with a more meaningful description and a justification why
a new thread flag is needed.
Thanks.
--
Catalin
prev parent reply other threads:[~2025-06-30 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 17:37 [PATCH v4] arm64: Implement HAVE_LIVEPATCH Song Liu
2025-06-26 13:21 ` Will Deacon
2025-06-26 14:55 ` Song Liu
2025-06-30 17:16 ` Catalin Marinas [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=aGLGf5feF4gT-dgR@arm.com \
--to=catalin.marinas@arm.com \
--cc=andrea.porta@suse.com \
--cc=duwe@suse.de \
--cc=dylanbhatch@google.com \
--cc=fj6611ie@aa.jp.fujitsu.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=song@kernel.org \
--cc=surajjs@amazon.com \
--cc=will@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).