From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: stable@vger.kernel.org, anshuman.khandual@arm.com,
bwicaksono@nvidia.com, catalin.marinas@arm.com,
james.clark@arm.com, james.morse@arm.com, will@kernel.org
Subject: Re: [PATCH 6.6.y 13/13] arm64: errata: Expand speculative SSBS workaround (again)
Date: Thu, 15 Aug 2024 17:05:08 +0200 [thread overview]
Message-ID: <2024081501-dispute-underwear-a9ca@gregkh> (raw)
In-Reply-To: <Zr4V_T8_ugiJmGJg@J2N7QTR9R3.cambridge.arm.com>
On Thu, Aug 15, 2024 at 03:51:41PM +0100, Mark Rutland wrote:
> On Mon, Aug 12, 2024 at 05:03:45PM +0200, Greg KH wrote:
> > On Fri, Aug 09, 2024 at 10:57:45AM +0100, Mark Rutland wrote:
> > > [ Upstream commit b0672bbe133ebb6f7be21fce1d742d52f25bcdc7 ]
> >
> > Now I figured it out, this is the wrong git id, and is not in any tree
> > anywhere. It should be adeec61a4723fd3e39da68db4cc4d924e6d7f641.
> >
> > I'll go hand-edit it now...
>
> Thanks, and sorry about that.
>
> Looking in my local tree, the incorrect commit id is a copy of
> adeec61a4723fd3e39da68db4cc4d924e6d7f641 where the earlier commits had
> been updated with "[ Upstream commit XXX ]" wording. Evidently I grabbed
> the commit ID from the wrong branch when I was folding that in.
>
> I'll try to make sure that doesn't happen again. Is there any public
> tooling for sanity-checking this?
Not that I know of :(
prev parent reply other threads:[~2024-08-15 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 9:57 [PATCH 6.6.y 0/13] arm64: errata: Speculative SSBS workaround Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 01/13] arm64: Add Neoverse-V2 part Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 02/13] arm64: barrier: Restore spec_bar() macro Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 03/13] arm64: cputype: Add Cortex-X4 definitions Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 04/13] arm64: cputype: Add Neoverse-V3 definitions Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 05/13] arm64: errata: Add workaround for Arm errata 3194386 and 3312417 Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 06/13] arm64: cputype: Add Cortex-X3 definitions Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 07/13] arm64: cputype: Add Cortex-A720 definitions Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 08/13] arm64: cputype: Add Cortex-X925 definitions Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 09/13] arm64: errata: Unify speculative SSBS errata logic Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 10/13] arm64: errata: Expand speculative SSBS workaround Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 11/13] arm64: cputype: Add Cortex-X1C definitions Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 12/13] arm64: cputype: Add Cortex-A725 definitions Mark Rutland
2024-08-09 9:57 ` [PATCH 6.6.y 13/13] arm64: errata: Expand speculative SSBS workaround (again) Mark Rutland
2024-08-12 15:03 ` Greg KH
2024-08-15 14:51 ` Mark Rutland
2024-08-15 15:05 ` Greg KH [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=2024081501-dispute-underwear-a9ca@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anshuman.khandual@arm.com \
--cc=bwicaksono@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=james.clark@arm.com \
--cc=james.morse@arm.com \
--cc=mark.rutland@arm.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