From: Henry Sloan <henryksloan@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: pbonzini@redhat.com, Henry Sloan <henryksloan@gmail.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 5/7] KVM: Use typical style for block comments
Date: Sat, 5 Mar 2022 22:19:05 -0500 [thread overview]
Message-ID: <20220306031907.210499-7-henryksloan@gmail.com> (raw)
In-Reply-To: <20220306031907.210499-1-henryksloan@gmail.com>
Adjusted spacing and line breaks for some comments so that the
asterisks align properly.
Signed-off-by: Henry Sloan <henryksloan@gmail.com>
---
virt/kvm/irqchip.c | 6 ++++--
virt/kvm/kvm_main.c | 6 +++---
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/virt/kvm/irqchip.c b/virt/kvm/irqchip.c
index 69a327c043d7..80708f6ec9d9 100644
--- a/virt/kvm/irqchip.c
+++ b/virt/kvm/irqchip.c
@@ -120,8 +120,10 @@ static void free_irq_routing_table(struct kvm_irq_routing_table *rt)
void kvm_free_irq_routing(struct kvm *kvm)
{
- /* Called only during vm destruction. Nobody can use the pointer
- at this stage */
+ /*
+ * Called only during vm destruction. Nobody can use the pointer
+ * at this stage
+ */
struct kvm_irq_routing_table *rt = rcu_access_pointer(kvm->irq_routing);
free_irq_routing_table(rt);
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index 1988dd081606..1a9f20e3fa2d 100644
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -2182,7 +2182,7 @@ static int kvm_clear_dirty_log_protect(struct kvm *kvm,
* never includes any bits beyond the length of the memslot (if
* the length is not aligned to 64 pages), therefore it is not
* a problem if userspace sets them in log->dirty_bitmap.
- */
+ */
if (mask) {
flush = true;
kvm_arch_mmu_enable_log_dirty_pt_masked(kvm, memslot,
@@ -5245,8 +5245,8 @@ static int kvm_debugfs_open(struct inode *inode, struct file *file,
/*
* The debugfs files are a reference to the kvm struct which
- * is still valid when kvm_destroy_vm is called. kvm_get_kvm_safe
- * avoids the race between open and the removal of the debugfs directory.
+ * is still valid when kvm_destroy_vm is called. kvm_get_kvm_safe
+ * avoids the race between open and the removal of the debugfs directory.
*/
if (!kvm_get_kvm_safe(stat_data->kvm))
return -ENOENT;
--
2.35.1
next prev parent reply other threads:[~2022-03-06 3:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220306031907.210499-1-henryksloan@gmail.com>
2022-03-06 3:19 ` [PATCH v2] KVM: Fix minor indentation and brace style issues Henry Sloan
2022-03-06 3:19 ` [PATCH v2 1/7] KVM: Use typical SPDX comment style Henry Sloan
2022-03-06 3:19 ` [PATCH v2 2/7] KVM: Replace bare 'unsigned' with 'unsigned int' Henry Sloan
2022-03-06 3:19 ` [PATCH v2 3/7] KVM: Replace '__attribute__((weak))' with '__weak' Henry Sloan
2022-03-06 3:19 ` [PATCH v2 4/7] KVM: Add blank lines after some declarations Henry Sloan
2022-03-06 3:19 ` Henry Sloan [this message]
2022-03-06 3:19 ` [PATCH v2 6/7] KVM: Fix minor indentation and brace style issues Henry Sloan
2022-03-06 3:19 ` [PATCH v2 7/7] KVM: Modified two MMIO functions to return bool Henry Sloan
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=20220306031907.210499-7-henryksloan@gmail.com \
--to=henryksloan@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®