From: Haowen Hu <src.res.211@gmail.com>
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org, tglx@linutronix.de,
bp@alien8.de, x86@kernel.org, hpa@zytor.com
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
src.res.211@gmail.com
Subject: [PATCH] perf/x86: Improve code format
Date: Sun, 16 May 2021 16:08:54 +0800 [thread overview]
Message-ID: <523745bf-c399-dc2e-ac57-1d580254802a@gmail.com> (raw)
Reformatted several lines of code, in order to satisfy the kernel code
format.
Signed-off-by: Haowen Hu <src.res.211@gmail.com>
---
arch/x86/events/core.c | 2 +-
arch/x86/events/rapl.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
index 8e509325c2c3..8cd61beb97e7 100644
--- a/arch/x86/events/core.c
+++ b/arch/x86/events/core.c
@@ -2829,7 +2829,7 @@ perf_callchain_user32(struct pt_regs *regs, struct
perf_callchain_entry_ctx *ent
static inline int
perf_callchain_user32(struct pt_regs *regs, struct
perf_callchain_entry_ctx *entry)
{
- return 0;
+ return 0;
}
#endif
diff --git a/arch/x86/events/rapl.c b/arch/x86/events/rapl.c
index 84a1042c3b01..da43975d9929 100644
--- a/arch/x86/events/rapl.c
+++ b/arch/x86/events/rapl.c
@@ -131,7 +131,7 @@ struct rapl_model {
enum rapl_unit_quirk unit_quirk;
};
- /* 1/2^hw_unit Joule */
+/* 1/2^hw_unit Joule */
static int rapl_hw_unit[NR_RAPL_DOMAINS] __read_mostly;
static struct rapl_pmus *rapl_pmus;
static cpumask_t rapl_cpu_mask;
@@ -209,7 +209,7 @@ static u64 rapl_event_update(struct perf_event *event)
static void rapl_start_hrtimer(struct rapl_pmu *pmu)
{
- hrtimer_start(&pmu->hrtimer, pmu->timer_interval,
+ hrtimer_start(&pmu->hrtimer, pmu->timer_interval,
HRTIMER_MODE_REL_PINNED);
}
--
2.25.1
next reply other threads:[~2021-05-16 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 8:08 Haowen Hu [this message]
2021-05-16 12:15 ` [PATCH] perf/x86: Improve code format Peter Zijlstra
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=523745bf-c399-dc2e-ac57-1d580254802a@gmail.com \
--to=src.res.211@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--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