public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christoph Schlameuss" <schlameuss@linux.ibm.com>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Christian Borntraeger" <borntraeger@de.ibm.com>,
	"Janosch Frank" <frankja@linux.ibm.com>,
	"KVM" <kvm@vger.kernel.org>, "S390" <linux-s390@vger.kernel.org>
Cc: "Claudio Imbrenda" <imbrenda@linux.ibm.com>,
	"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 kvms390-fixes tree
Date: Tue, 07 Jan 2025 13:35:15 +0100	[thread overview]
Message-ID: <D6VUFLL8PPTQ.1VZ6VWPZWRVTD@linux.ibm.com> (raw)
In-Reply-To: <20250106064232.3c34fdb1@canb.auug.org.au>

On Sun Jan 5, 2025 at 8:42 PM CET, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
>   6c2b70cc4887 ("selftests: kvm: s390: Streamline uc_skey test to issue iske after sske")
>
> Fixes tag
>
>   Fixes: 7d900f8ac191 ("selftests: kvm: s390: Add uc_skey VM test case")
>
> has these problem(s):
>
>   - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 0185fbc6a2d3 ("KVM: s390: selftests: Add uc_skey VM test case")

Yes, I double checked. Your proposal is the correct hash / commit on the master
branch.
Sorry for the mixup.

  reply	other threads:[~2025-01-07 12:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-05 19:42 linux-next: Fixes tag needs some work in the kvms390-fixes tree Stephen Rothwell
2025-01-07 12:35 ` Christoph Schlameuss [this message]
2025-01-07 15:40 ` Claudio Imbrenda
  -- strict thread matches above, loose matches on Subject: below --
2020-03-10 22:01 Stephen Rothwell

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=D6VUFLL8PPTQ.1VZ6VWPZWRVTD@linux.ibm.com \
    --to=schlameuss@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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