From: Marc Zyngier <maz@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Christoffer Dall <cdall@cs•columbia.edu>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the kvm-arm tree
Date: Tue, 23 Apr 2024 01:42:21 +0100 [thread overview]
Message-ID: <87ttjsucya.wl-maz@kernel.org> (raw)
In-Reply-To: <20240423092557.73c2ec1b@canb.auug.org.au>
On Tue, 23 Apr 2024 00:25:57 +0100,
Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
> fe4763e18355 ("KVM: arm64: nv: Work around lack of pauth support in old toolchains")
>
> Fixes tag
>
> Fixes: e09faab353a6 ("KVM: arm64: nv: Add emulation for ERETAx instructions")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 6ccc971ee2c6 ("KVM: arm64: nv: Add emulation for ERETAx instructions")
Indeed. Thanks for spotting this. Fixed and pushed out.
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2024-04-23 0:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 23:25 linux-next: Fixes tag needs some work in the kvm-arm tree Stephen Rothwell
2024-04-23 0:42 ` Marc Zyngier [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=87ttjsucya.wl-maz@kernel.org \
--to=maz@kernel$(echo .)org \
--cc=cdall@cs$(echo .)columbia.edu \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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