linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emil Bartczak <emilbart@gmail.com>
To: a.zummo@towertech.it
Cc: alexandre.belloni@free-electrons.com, rtc-linux@googlegroups.com,
	linux-kernel@vger.kernel.org, Emil Bartczak <emilbart@gmail.com>
Subject: [PATCH v2 6/6] rtc: mcp795: Fix whitespace and indentation.
Date: Thu,  8 Dec 2016 00:27:42 +0100	[thread overview]
Message-ID: <588ddbf1ec3c6c14e6650ab9b5414d8ac4f4e36a.1481151278.git.emilbart@gmail.com> (raw)
In-Reply-To: <cover.1481151278.git.emilbart@gmail.com>
In-Reply-To: <cover.1481151278.git.emilbart@gmail.com>

Fix whitespace and indentation errors and the following
checkpatch warnings:
- line 15: Block comments use a trailing */ on a separate line
- line 256: Line over 80 characters
No code change.

Signed-off-by: Emil Bartczak <emilbart@gmail.com>
---
 drivers/rtc/rtc-mcp795.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/drivers/rtc/rtc-mcp795.c b/drivers/rtc/rtc-mcp795.c
index 8ed55f6..ce75e42 100644
--- a/drivers/rtc/rtc-mcp795.c
+++ b/drivers/rtc/rtc-mcp795.c
@@ -12,7 +12,7 @@
  * it under the terms of the GNU General Public License version 2 as
  * published by the Free Software Foundation.
  *
- * */
+ */
 
 #include <linux/module.h>
 #include <linux/kernel.h>
@@ -31,7 +31,7 @@
 #define MCP795_EEWREN	0x06
 #define MCP795_SRREAD	0x05
 #define MCP795_SRWRITE	0x01
-#define MCP795_READ		0x13
+#define MCP795_READ	0x13
 #define MCP795_WRITE	0x12
 #define MCP795_UNLOCK	0x14
 #define MCP795_IDWRITE	0x32
@@ -45,9 +45,9 @@
 #define MCP795_REG_MONTH	0x06
 #define MCP795_REG_CONTROL	0x08
 
-#define MCP795_ST_BIT	BIT(7)
-#define MCP795_24_BIT	BIT(6)
-#define MCP795_LP_BIT	BIT(5)
+#define MCP795_ST_BIT		BIT(7)
+#define MCP795_24_BIT		BIT(6)
+#define MCP795_LP_BIT		BIT(5)
 #define MCP795_EXTOSC_BIT	BIT(3)
 #define MCP795_OSCON_BIT	BIT(5)
 
@@ -253,7 +253,7 @@ static int mcp795_probe(struct spi_device *spi)
 	mcp795_rtcc_set_bits(&spi->dev, 0x03, MCP795_24_BIT, 0);
 
 	rtc = devm_rtc_device_register(&spi->dev, "rtc-mcp795",
-								&mcp795_rtc_ops, THIS_MODULE);
+					&mcp795_rtc_ops, THIS_MODULE);
 	if (IS_ERR(rtc))
 		return PTR_ERR(rtc);
 
-- 
2.7.4

  parent reply	other threads:[~2016-12-07 23:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 23:27 [PATCH v2 0/6] Provides bug fixes for rtc-mcp795.c Emil Bartczak
2016-12-07 23:27 ` [PATCH v2 1/6] rtc: mcp795: use bcd2bin/bin2bcd Emil Bartczak
2016-12-07 23:27 ` [PATCH v2 2/6] rtc: mcp795: fix bitmask value for leap year (LP) Emil Bartczak
2016-12-07 23:27 ` [PATCH v2 3/6] rtc: mcp795: fix time range difference between linux and RTC chip Emil Bartczak
2016-12-07 23:27 ` [PATCH v2 4/6] rtc: mcp795: fix month write resetting date to 1 Emil Bartczak
2016-12-07 23:27 ` [PATCH v2 5/6] rtc: mcp795: Prefer using the BIT() macro Emil Bartczak
2016-12-07 23:27 ` Emil Bartczak [this message]
2016-12-08  0:34 ` [PATCH v2 0/6] Provides bug fixes for rtc-mcp795.c Alexandre Belloni

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=588ddbf1ec3c6c14e6650ab9b5414d8ac4f4e36a.1481151278.git.emilbart@gmail.com \
    --to=emilbart@gmail.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    /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).