From: Janosch Frank <frankja@linux.ibm.com>
To: pbonzini@redhat.com
Cc: kvm@vger.kernel.org, frankja@linux.ibm.com, david@redhat.com,
borntraeger@linux.ibm.com, cohuck@redhat.com,
linux-s390@vger.kernel.org, imbrenda@linux.ibm.com
Subject: [GIT PULL 0/2] KVM: s390: updates for 6.15
Date: Sat, 22 Mar 2025 12:06:43 +0100 [thread overview]
Message-ID: <20250322111119.24548-1-frankja@linux.ibm.com> (raw)
Paolo,
only two cleanup patches by Thomas Weissschuh fixing our pointer print
formats in s390 KVM.
I'll be on a conference next week but I'll check my mails periodically
and I really don't expect problems with those two patches.
Please pull.
Cheers,
Janosch
The following changes since commit a64dcfb451e254085a7daee5fe51bf22959d52d3:
Linux 6.14-rc2 (2025-02-09 12:45:03 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-next-6.15-1
for you to fetch changes up to 0c7fbae5bc782429c97d68dc40fb126748d7e352:
KVM: s390: Don't use %pK through debug printing (2025-03-17 08:55:46 +0000)
----------------------------------------------------------------
Pointer print format fixes
----------------------------------------------------------------
Thomas Weißschuh (2):
KVM: s390: Don't use %pK through tracepoints
KVM: s390: Don't use %pK through debug printing
arch/s390/kvm/intercept.c | 2 +-
arch/s390/kvm/interrupt.c | 8 ++++----
arch/s390/kvm/kvm-s390.c | 10 +++++-----
arch/s390/kvm/trace-s390.h | 4 ++--
4 files changed, 12 insertions(+), 12 deletions(-)
--
2.49.0
next reply other threads:[~2025-03-22 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 11:06 Janosch Frank [this message]
2025-03-22 11:06 ` [GIT PULL 1/2] KVM: s390: Don't use %pK through tracepoints Janosch Frank
2025-03-22 11:06 ` [GIT PULL 2/2] KVM: s390: Don't use %pK through debug printing Janosch Frank
2025-03-31 10:09 ` [GIT PULL 0/2] KVM: s390: updates for 6.15 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=20250322111119.24548-1-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@linux.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