From: Ralph Sennhauser <ralph.sennhauser@gmail.com>
To: linux-gpio@vger.kernel.org
Cc: Ralph Sennhauser <ralph.sennhauser@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 2/6] gpio: mvebu: start multiline block comments with blank line
Date: Thu, 16 Mar 2017 07:33:57 +0100 [thread overview]
Message-ID: <20170316063402.8667-3-ralph.sennhauser@gmail.com> (raw)
In-Reply-To: <20170316063402.8667-1-ralph.sennhauser@gmail.com>
While this isn't an issue according to checkpatch two styles are used.
Add a blank line to the block comments missing a blank line at the start
so multiline block comments look the same across the file.
Signed-off-by: Ralph Sennhauser <ralph.sennhauser@gmail.com>
---
drivers/gpio/gpio-mvebu.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/gpio/gpio-mvebu.c b/drivers/gpio/gpio-mvebu.c
index a2351f3..80b1d52 100644
--- a/drivers/gpio/gpio-mvebu.c
+++ b/drivers/gpio/gpio-mvebu.c
@@ -788,7 +788,8 @@ static int mvebu_gpio_probe(struct platform_device *pdev)
goto err_domain;
}
- /* NOTE: The common accessors cannot be used because of the percpu
+ /*
+ * NOTE: The common accessors cannot be used because of the percpu
* access to the mask registers
*/
gc = irq_get_domain_generic_chip(mvchip->domain, 0);
@@ -809,7 +810,8 @@ static int mvebu_gpio_probe(struct platform_device *pdev)
ct->handler = handle_edge_irq;
ct->chip.name = mvchip->chip.label;
- /* Setup the interrupt handlers. Each chip can have up to 4
+ /*
+ * Setup the interrupt handlers. Each chip can have up to 4
* interrupt handlers, with each handler dealing with 8 GPIO
* pins.
*/
--
2.10.2
next prev parent reply other threads:[~2017-03-16 6:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 6:33 [PATCH 0/6] gpio: mvebu: prepatatory cleanup for pwm-fan support Ralph Sennhauser
2017-03-16 6:33 ` [PATCH 1/6] gpio: mvebu: checkpatch: block comment fixes Ralph Sennhauser
2017-03-16 15:40 ` Linus Walleij
2017-03-16 6:33 ` Ralph Sennhauser [this message]
2017-03-16 15:41 ` [PATCH 2/6] gpio: mvebu: start multiline block comments with blank line Linus Walleij
2017-03-16 6:33 ` [PATCH 3/6] gpio: mvebu: checkpatch: unsigned int fixes Ralph Sennhauser
2017-03-16 15:42 ` Linus Walleij
2017-03-16 6:33 ` [PATCH 4/6] gpio: mvebu: checkpatch: whitespace fixes Ralph Sennhauser
2017-03-16 15:42 ` Linus Walleij
2017-03-16 6:34 ` [PATCH 5/6] gpio: mvebu: extra " Ralph Sennhauser
2017-03-16 15:43 ` Linus Walleij
2017-03-16 6:34 ` [PATCH 6/6] gpio: mvebu: let the compiler inline Ralph Sennhauser
2017-03-16 15:44 ` Linus Walleij
2017-03-17 9:08 ` Ralph Sennhauser
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=20170316063402.8667-3-ralph.sennhauser@gmail.com \
--to=ralph.sennhauser@gmail.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome