From: Catalin Marinas <catalin.marinas@arm.com>
To: Easwar Hariharan <eahariha@linux.microsoft.com>
Cc: Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Mark Rutland <mark.rutland@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Rob Herring <robh@kernel.org>,
D Scott Phillips <scott@os.amperecomputing.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, James More <james.morse@arm.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] arm64: Subscribe Microsoft Azure Cobalt 100 to erratum 3194386
Date: Fri, 4 Oct 2024 19:31:00 +0300 [thread overview]
Message-ID: <ZwAYRH208DS-HDpV@arm.com> (raw)
In-Reply-To: <f64f2cb8-de7a-4131-a0ae-e986b4857777@linux.microsoft.com>
On Fri, Oct 04, 2024 at 09:24:15AM -0700, Easwar Hariharan wrote:
> On 10/4/2024 4:47 AM, Catalin Marinas wrote:
> > On Thu, 03 Oct 2024 22:52:35 +0000, Easwar Hariharan wrote:
> >> Add the Microsoft Azure Cobalt 100 CPU to the list of CPUs suffering
> >> from erratum 3194386 added in commit 75b3c43eab59 ("arm64: errata:
> >> Expand speculative SSBS workaround")
> >
> > Applied to arm64 (for-next/fixes), thanks!
> >
> > [1/1] arm64: Subscribe Microsoft Azure Cobalt 100 to erratum 3194386
> > https://git.kernel.org/arm64/c/3eddb108abe3
> >
>
> Thanks for queuing, I just saw that I typoed James' last name in the CC
> of the commit message. i.e. it needs s/More/Morse/
>
> I'll let you decide if it needs fixing up.
Too late, I already sent the pull request to Linus. I doubt anyone else
would notice ;).
--
Catalin
prev parent reply other threads:[~2024-10-04 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 22:52 [PATCH] arm64: Subscribe Microsoft Azure Cobalt 100 to erratum 3194386 Easwar Hariharan
2024-10-04 11:47 ` Catalin Marinas
2024-10-04 16:24 ` Easwar Hariharan
2024-10-04 16:31 ` 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=ZwAYRH208DS-HDpV@arm.com \
--to=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=eahariha@linux.microsoft.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=oliver.upton@linux.dev \
--cc=robh@kernel.org \
--cc=scott@os.amperecomputing.com \
--cc=stable@vger.kernel.org \
--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).