From: Nico Boehr <nrb@linux.ibm.com>
To: borntraeger@linux.ibm.com, frankja@linux.ibm.com,
imbrenda@linux.ibm.com, david@redhat.com
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [PATCH v1 1/3] KVM: s390: fix space before open parenthesis
Date: Tue, 9 May 2023 13:12:00 +0200 [thread overview]
Message-ID: <20230509111202.333714-2-nrb@linux.ibm.com> (raw)
In-Reply-To: <20230509111202.333714-1-nrb@linux.ibm.com>
There should be a space before the open parenthesis, fix that while at
it.
Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
---
arch/s390/include/asm/kvm_host.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/s390/include/asm/kvm_host.h b/arch/s390/include/asm/kvm_host.h
index 2bbc3d54959d..3c3fe45085ec 100644
--- a/arch/s390/include/asm/kvm_host.h
+++ b/arch/s390/include/asm/kvm_host.h
@@ -947,7 +947,7 @@ struct kvm_s390_pv {
struct mmu_notifier mmu_notifier;
};
-struct kvm_arch{
+struct kvm_arch {
void *sca;
int use_esca;
rwlock_t sca_lock;
--
2.39.1
next prev parent reply other threads:[~2023-05-09 11:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 11:11 [PATCH v1 0/3] KVM: s390: add counters for vsie performance Nico Boehr
2023-05-09 11:12 ` Nico Boehr [this message]
2023-05-09 11:19 ` [PATCH v1 1/3] KVM: s390: fix space before open parenthesis Claudio Imbrenda
2023-05-09 11:12 ` [PATCH v1 2/3] KVM: s390: add stat counter for shadow gmap events Nico Boehr
2023-05-09 11:43 ` Claudio Imbrenda
2023-05-09 14:53 ` Nico Boehr
2023-05-09 15:17 ` Claudio Imbrenda
2023-05-09 11:59 ` Janosch Frank
2023-05-09 14:54 ` Nico Boehr
2023-05-09 15:14 ` Claudio Imbrenda
2023-05-10 6:45 ` Janosch Frank
2023-05-09 11:12 ` [PATCH v1 3/3] KVM: s390: add tracepoint in gmap notifier Nico Boehr
2023-05-09 11:48 ` Claudio Imbrenda
2023-05-09 14:54 ` Nico Boehr
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=20230509111202.333714-2-nrb@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/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