From: Will Deacon <will@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: "haibinzhang(张海斌)" <haibinzhang@tencent.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Ard Biesheuvel" <ard.biesheuvel@arm.com>,
"Martin Ma" <Martin.Ma@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hewenliang4@huawei.com" <hewenliang4@huawei.com>
Subject: Re: [PATCH V2] arm64: fix oops in concurrently setting insn_emulation sysctls
Date: Wed, 20 Jul 2022 17:11:11 +0100 [thread overview]
Message-ID: <20220720161110.GA16493@willie-the-truck> (raw)
In-Reply-To: <YtggOdLN5NuFkFrl@google.com>
On Wed, Jul 20, 2022 at 04:33:13PM +0100, Lee Jones wrote:
> On Wed, 20 Jul 2022, Will Deacon wrote:
> > On the plus side, the patch has a Link: tag to this thread, so the
> > Fixes tag is retrievable if you're determined enough.
> >
> > If somebody wants this for stable, then I suppose they'll have to send
> > a backport to make sure it doesn't get missed.
>
> I'll add it to my TODO.
Brill, thanks Lee.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: "haibinzhang(张海斌)" <haibinzhang@tencent.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Ard Biesheuvel" <ard.biesheuvel@arm.com>,
"Martin Ma" <Martin.Ma@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hewenliang4@huawei.com" <hewenliang4@huawei.com>
Subject: Re: [PATCH V2] arm64: fix oops in concurrently setting insn_emulation sysctls
Date: Wed, 20 Jul 2022 17:11:11 +0100 [thread overview]
Message-ID: <20220720161110.GA16493@willie-the-truck> (raw)
In-Reply-To: <YtggOdLN5NuFkFrl@google.com>
On Wed, Jul 20, 2022 at 04:33:13PM +0100, Lee Jones wrote:
> On Wed, 20 Jul 2022, Will Deacon wrote:
> > On the plus side, the patch has a Link: tag to this thread, so the
> > Fixes tag is retrievable if you're determined enough.
> >
> > If somebody wants this for stable, then I suppose they'll have to send
> > a backport to make sure it doesn't get missed.
>
> I'll add it to my TODO.
Brill, thanks Lee.
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-20 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 5:43 [PATCH V2] arm64: fix oops in concurrently setting insn_emulation sysctls haibinzhang(张海斌)
2022-07-02 5:43 ` haibinzhang(张海斌)
2022-07-04 10:34 ` Catalin Marinas
2022-07-04 10:34 ` Catalin Marinas
2022-07-04 14:27 ` Will Deacon
2022-07-04 14:27 ` Will Deacon
2022-07-20 12:23 ` Lee Jones
2022-07-20 12:23 ` Lee Jones
2022-07-20 15:13 ` Will Deacon
2022-07-20 15:13 ` Will Deacon
2022-07-20 15:33 ` Lee Jones
2022-07-20 15:33 ` Lee Jones
2022-07-20 16:11 ` Will Deacon [this message]
2022-07-20 16:11 ` Will Deacon
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=20220720161110.GA16493@willie-the-truck \
--to=will@kernel.org \
--cc=Martin.Ma@arm.com \
--cc=ard.biesheuvel@arm.com \
--cc=catalin.marinas@arm.com \
--cc=haibinzhang@tencent.com \
--cc=hewenliang4@huawei.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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.