From: Janosch Frank <frankja@linux.ibm.com>
To: pbonzini@redhat.com
Cc: kvm@vger.kernel.org, frankja@linux.ibm.com, david@redhat.com,
borntraeger@de.ibm.com, cohuck@redhat.com,
linux-s390@vger.kernel.org, imbrenda@linux.ibm.com
Subject: [GIT PULL 0/1] s390 fixes for 6.1-rc7/8
Date: Fri, 25 Nov 2022 09:54:53 +0100 [thread overview]
Message-ID: <20221125085454.16673-1-frankja@linux.ibm.com> (raw)
Dear Paolo,
please pull Thomas' fix for VSIE.
We deem it to be low risk and it survived a day in our CI without any errors.
It's a bit late so let's see if it makes 6.1 or 6.2.
The following changes since commit eb7081409f94a9a8608593d0fb63a1aa3d6f95d8:
Linux 6.1-rc6 (2022-11-20 16:02:16 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-master-6.1-2
for you to fetch changes up to 0dd4cdccdab3d74bd86b868768a7dca216bcce7e:
KVM: s390: vsie: Fix the initialization of the epoch extension (epdx) field (2022-11-24 14:43:17 +0100)
----------------------------------------------------------------
VSIE epdx shadowing fix
----------------------------------------------------------------
Thomas Huth (1):
KVM: s390: vsie: Fix the initialization of the epoch extension (epdx) field
arch/s390/kvm/vsie.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Thomas Huth (1):
KVM: s390: vsie: Fix the initialization of the epoch extension (epdx)
field
arch/s390/kvm/vsie.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
2.38.1
next reply other threads:[~2022-11-25 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 8:54 Janosch Frank [this message]
2022-11-25 8:54 ` [GIT PULL 1/1] KVM: s390: vsie: Fix the initialization of the epoch extension (epdx) field Janosch Frank
2022-11-29 15:14 ` [GIT PULL 0/1] s390 fixes for 6.1-rc7/8 Paolo Bonzini
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=20221125085454.16673-1-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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