From: Jagath Jog J <jagathjog1996@gmail.com>
To: alexandre.belloni@bootlin.com, a.zummo@towertech.it
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
jagathjog1996@gmail.com
Subject: [PATCH 3/3] rtc: rv3028: Alignment to match the open parenthesis
Date: Tue, 16 Aug 2022 09:26:36 +0530 [thread overview]
Message-ID: <20220816035636.27226-4-jagathjog1996@gmail.com> (raw)
In-Reply-To: <20220816035636.27226-1-jagathjog1996@gmail.com>
Fix following checkpatch.pl check by adding space to match the
open parenthesis and removing unwanted blank line.
CHECK: Alignment should match open parenthesis.
CHECK: Blank lines aren't necessary before a close brace '}'.
Signed-off-by: Jagath Jog J <jagathjog1996@gmail.com>
---
drivers/rtc/rtc-rv3028.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-rv3028.c b/drivers/rtc/rtc-rv3028.c
index f7c801c06d00..0da68fd7cedd 100644
--- a/drivers/rtc/rtc-rv3028.c
+++ b/drivers/rtc/rtc-rv3028.c
@@ -266,7 +266,7 @@ static irqreturn_t rv3028_handle_irq(int irq, void *dev_id)
u32 status = 0, ctrl = 0;
if (regmap_read(rv3028->regmap, RV3028_STATUS, &status) < 0 ||
- status == 0) {
+ status == 0) {
return IRQ_NONE;
}
@@ -514,7 +514,6 @@ static int rv3028_set_offset(struct device *dev, long offset)
rv3028_exit_eerd(rv3028, eerd);
return ret;
-
}
static int rv3028_param_get(struct device *dev, struct rtc_param *param)
--
2.17.1
prev parent reply other threads:[~2022-08-16 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 3:56 [PATCH 0/3] rtc: rv3028: Fix codestyle errors and checks Jagath Jog J
2022-08-16 3:56 ` [PATCH 1/3] rtc: rv3028: Inserting some required spaces Jagath Jog J
2022-08-16 3:56 ` [PATCH 2/3] rtc: rv3028: fix code indent issue Jagath Jog J
2022-08-16 3:56 ` Jagath Jog J [this message]
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=20220816035636.27226-4-jagathjog1996@gmail.com \
--to=jagathjog1996@gmail.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@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 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®