From: "Kaya, Metin" <metikaya@amazon.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [kvm-unit-tests PATCH 2/2] x86/smptest: Fix whitespacing issues
Date: Tue, 4 Jan 2022 12:51:44 +0000 [thread overview]
Message-ID: <1641300703862.58592@amazon.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 126 bytes --]
The convention is using spaces in x86/smptest.c. However, tab was used in 2 places. Replaced them with spaces.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0002-x86-smptest-Fix-whitespacing-issues.patch --]
[-- Type: text/x-patch; name="0002-x86-smptest-Fix-whitespacing-issues.patch", Size: 1120 bytes --]
From aa35cf403ef2296afb20cbe96cf771495eebcd99 Mon Sep 17 00:00:00 2001
From: Metin Kaya <metikaya@amazon.com>
Date: Wed, 22 Dec 2021 18:25:20 +0000
Subject: [kvm-unit-tests PATCH 2/2] x86/smptest: Fix whitespacing issues
The convention is using spaces in x86/smptest.c. However, tab was used
in 2 places. Replaced them with spaces.
Signed-off-by: Metin Kaya <metikaya@amazon.com>
---
x86/smptest.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/x86/smptest.c b/x86/smptest.c
index 2989aa0..6391759 100644
--- a/x86/smptest.c
+++ b/x86/smptest.c
@@ -9,7 +9,7 @@ static void ipi_test(void *data)
printf("ipi called, cpu %d\n", n);
if (n != smp_id())
- printf("but wrong cpu %d\n", smp_id());
+ printf("but wrong cpu %d\n", smp_id());
else
nipis++;
}
@@ -22,7 +22,7 @@ int main(void)
ncpus = cpu_count();
printf("found %d cpus\n", ncpus);
for (i = 0; i < ncpus; ++i)
- on_cpu(i, ipi_test, (void *)(long)i);
+ on_cpu(i, ipi_test, (void *)(long)i);
report(nipis == ncpus, "IPI to each CPU");
return report_summary();
--
2.32.0
next reply other threads:[~2022-01-04 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 12:51 Kaya, Metin [this message]
2022-01-04 15:24 ` [kvm-unit-tests PATCH 2/2] x86/smptest: Fix whitespacing issues Kaya, Metin
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=1641300703862.58592@amazon.com \
--to=metikaya@amazon.com \
--cc=kvm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.