public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: shijie001@208suo.com
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, x86@kernel.org
Cc: hpa@zytor.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	seanjc@google.com, pbonzini@redhat.com
Subject: [PATCH] KVM: x86: Fix error & warning in i8254.h
Date: Wed, 12 Jul 2023 14:02:35 +0800	[thread overview]
Message-ID: <f1a0806ffdb74240f9bfbba9f4ece732@208suo.com> (raw)
In-Reply-To: <tencent_EA89B0582F8F8C3CC33C9F7AE407FC956F09@qq.com>

The following checkpatch error & warning are removed:
WARNING: please, no space before tabs
ERROR: Macros with complex values should be enclosed in parentheses

Signed-off-by: Jie Shi <shijie001@208suo.com>
---
  arch/x86/kvm/i8254.h | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/kvm/i8254.h b/arch/x86/kvm/i8254.h
index a768212ba821..89eab61cfc51 100644
--- a/arch/x86/kvm/i8254.h
+++ b/arch/x86/kvm/i8254.h
@@ -27,7 +27,7 @@ struct kvm_kpit_state {
      struct kvm_kpit_channel_state channels[3];
      u32 flags;
      bool is_periodic;
-    s64 period;                 /* unit: ns */
+    s64 period;                /* unit: ns */
      struct hrtimer timer;

      struct mutex lock;
@@ -52,7 +52,7 @@ struct kvm_pit {
  #define KVM_SPEAKER_BASE_ADDRESS    0x61
  #define KVM_PIT_MEM_LENGTH        4
  #define KVM_PIT_FREQ            1193181
-#define KVM_MAX_PIT_INTR_INTERVAL   HZ / 100
+#define KVM_MAX_PIT_INTR_INTERVAL   (HZ / 100)
  #define KVM_PIT_CHANNEL_MASK        0x3

  struct kvm_pit *kvm_create_pit(struct kvm *kvm, u32 flags);

       reply	other threads:[~2023-07-12  6:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_EA89B0582F8F8C3CC33C9F7AE407FC956F09@qq.com>
2023-07-12  6:02 ` shijie001 [this message]
2023-07-18  6:48   ` [PATCH] KVM: x86: Fix error & warning in i8254.h Philippe Mathieu-Daudé

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=f1a0806ffdb74240f9bfbba9f4ece732@208suo.com \
    --to=shijie001@208suo.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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