From: Matthew Rosato <mjrosato@linux.ibm.com>
To: pbonzini@redhat.com
Cc: kvm@vger.kernel.org, borntraeger@linux.ibm.com,
imbrenda@linux.ibm.com, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: [PATCH 0/1] fix sparse warning in linux-next
Date: Thu, 4 Aug 2022 13:35:45 -0400 [thread overview]
Message-ID: <20220804173546.226968-1-mjrosato@linux.ibm.com> (raw)
Hi Paolo,
Sorry I missed the initial report on this while out of the office.
This patch fixes a sparse warning that shows up in
'KVM: s390: pci: do initial setup for AEN interpretation'
as part of the 5.20/6.0 pull request.
Matthew Rosato (1):
KVM: s390: pci: fix airq_iv_create sparse warning
arch/s390/kvm/pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.31.1
next reply other threads:[~2022-08-04 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 17:35 Matthew Rosato [this message]
2022-08-04 17:35 ` [PATCH 1/1] KVM: s390: pci: fix airq_iv_create sparse warning Matthew Rosato
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=20220804173546.226968-1-mjrosato@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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