linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jay Fang <f.fangjian@huawei.com>
To: <will@kernel.org>, <mark.rutland@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <linuxarm@huawei.com>,
	<huangdaode@huawei.com>, <hejunhao2@hisilicon.com>
Subject: [PATCH 4/4] drivers/perf: arm-cci: Fix checkpatch spacing error
Date: Tue, 11 May 2021 20:27:34 +0800	[thread overview]
Message-ID: <1620736054-58412-5-git-send-email-f.fangjian@huawei.com> (raw)
In-Reply-To: <1620736054-58412-1-git-send-email-f.fangjian@huawei.com>

From: Junhao He <hejunhao2@hisilicon.com>

Fix some coding style issues reported by checkpatch.pl, including
following types:

ERROR: need consistent spacing around '-' (ctx:WxV)
ERROR: space required before the open parenthesis '('

Signed-off-by: Junhao He <hejunhao2@hisilicon.com>
Signed-off-by: Jay Fang <f.fangjian@huawei.com>
---
 drivers/perf/arm-cci.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/perf/arm-cci.c b/drivers/perf/arm-cci.c
index 666d8a9..54aca3a6 100644
--- a/drivers/perf/arm-cci.c
+++ b/drivers/perf/arm-cci.c
@@ -37,7 +37,7 @@
 
 #define CCI_PMU_CNTR_SIZE(model)	((model)->cntr_size)
 #define CCI_PMU_CNTR_BASE(model, idx)	((idx) * CCI_PMU_CNTR_SIZE(model))
-#define CCI_PMU_CNTR_MASK		((1ULL << 32) -1)
+#define CCI_PMU_CNTR_MASK		((1ULL << 32) - 1)
 #define CCI_PMU_CNTR_LAST(cci_pmu)	(cci_pmu->num_cntrs - 1)
 
 #define CCI_PMU_MAX_HW_CNTRS(model) \
@@ -806,7 +806,7 @@ static int pmu_get_event_idx(struct cci_pmu_hw_events *hw, struct perf_event *ev
 		return cci_pmu->model->get_event_idx(cci_pmu, hw, cci_event);
 
 	/* Generic code to find an unused idx from the mask */
-	for(idx = 0; idx <= CCI_PMU_CNTR_LAST(cci_pmu); idx++)
+	for (idx = 0; idx <= CCI_PMU_CNTR_LAST(cci_pmu); idx++)
 		if (!test_and_set_bit(idx, hw->used_mask))
 			return idx;
 
-- 
2.8.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-05-11 13:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 12:27 [PATCH 0/4] drivers/perf: Fix ERRORs reported by checkpatch Jay Fang
2021-05-11 12:27 ` [PATCH 1/4] drivers/perf: arm_spe_pmu: Fix some coding style issues Jay Fang
2021-05-11 12:27 ` [PATCH 2/4] drivers/perf: arm_pmu: " Jay Fang
2021-05-11 12:27 ` [PATCH 3/4] drivers/perf: arm-cmn: Add space after ',' Jay Fang
2021-05-11 12:27 ` Jay Fang [this message]
2021-05-25 18:58 ` [PATCH 0/4] drivers/perf: Fix ERRORs reported by checkpatch Will Deacon

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=1620736054-58412-5-git-send-email-f.fangjian@huawei.com \
    --to=f.fangjian@huawei.com \
    --cc=hejunhao2@hisilicon.com \
    --cc=huangdaode@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxarm@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).