From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: clemens@ladisch.de, arnd@arndb.de, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, Corentin Labbe <clabbe.montjoie@gmail.com>
Subject: [PATCH v2 6/6] hpet: fix style issue about braces and alignment
Date: Mon, 3 Apr 2017 14:15:59 +0200 [thread overview]
Message-ID: <20170403121559.1397-7-clabbe.montjoie@gmail.com> (raw)
In-Reply-To: <20170403121559.1397-1-clabbe.montjoie@gmail.com>
This patch fix all style issue for braces and alignment
Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>
---
drivers/char/hpet.c | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/char/hpet.c b/drivers/char/hpet.c
index f6096e1..fe52f39 100644
--- a/drivers/char/hpet.c
+++ b/drivers/char/hpet.c
@@ -255,9 +255,9 @@ static int hpet_open(struct inode *inode, struct file *file)
for (devp = NULL, hpetp = hpets; hpetp && !devp; hpetp = hpetp->hp_next)
for (i = 0; i < hpetp->hp_ntimer; i++)
- if (hpetp->hp_dev[i].hd_flags & HPET_OPEN)
+ if (hpetp->hp_dev[i].hd_flags & HPET_OPEN) {
continue;
- else {
+ } else {
devp = &hpetp->hp_dev[i];
break;
}
@@ -304,9 +304,9 @@ hpet_read(struct file *file, char __user *buf, size_t count, loff_t *ppos)
devp->hd_irqdata = 0;
spin_unlock_irq(&hpet_lock);
- if (data)
+ if (data) {
break;
- else if (file->f_flags & O_NONBLOCK) {
+ } else if (file->f_flags & O_NONBLOCK) {
retval = -EAGAIN;
goto out;
} else if (signal_pending(current)) {
@@ -987,7 +987,8 @@ static acpi_status hpet_resources(struct acpi_resource *res, void *data)
break;
irq = acpi_register_gsi(NULL, irqp->interrupts[i],
- irqp->triggering, irqp->polarity);
+ irqp->triggering,
+ irqp->polarity);
if (irq < 0)
return AE_ERROR;
--
2.10.2
next prev parent reply other threads:[~2017-04-03 12:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 12:15 [PATCH v2 0/6] hpet: fix build warnings and style Corentin Labbe
2017-04-03 12:15 ` [PATCH v2 1/6] hpet: remove unused variable hpet in hpet_ioctl_common Corentin Labbe
2017-04-03 12:15 ` [PATCH v2 2/6] hpet: remove unused writeq/readq function definitions Corentin Labbe
2017-04-03 12:15 ` [PATCH v2 3/6] hpet: fix checkpatch complains about spaces Corentin Labbe
2017-04-03 12:15 ` [PATCH v2 4/6] hpet: replace printk by their pr_xxx counterparts Corentin Labbe
2017-04-03 19:44 ` Joe Perches
2017-04-03 12:15 ` [PATCH v2 5/6] hpet: removing unused variable m in hpet_interrupt Corentin Labbe
2017-04-03 12:55 ` Clemens Ladisch
2017-04-03 12:15 ` Corentin Labbe [this message]
2017-04-04 3:43 ` [PATCH v2 6/6] hpet: fix style issue about braces and alignment Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2017-03-30 2:53 [PATCH 0/2] Support new Alps HID I2C Touchpad device Masaki Ota
2017-03-30 2:53 ` [PATCH 1/2] Alps HID I2C T4 device support Masaki Ota
2017-04-04 3:08 ` Nikolaus Rath
2017-04-04 6:55 ` Masaki Ota
2017-04-04 17:08 ` Nikolaus Rath
2017-04-04 23:40 ` Masaki Ota
2017-04-04 23:42 ` Nikolaus Rath
2017-04-04 23:49 ` Masaki Ota
2017-04-05 0:01 ` Nikolaus Rath
2017-04-05 8:43 ` Masaki Ota
2017-04-05 18:35 ` Nikolaus Rath
2017-04-06 1:07 ` Masaki Ota
2017-04-06 22:59 ` Nikolaus Rath
2017-04-24 14:54 ` Benjamin Tissoires
2017-03-30 2:53 ` [PATCH 2/2] Add new U1 device ID Masaki Ota
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=20170403121559.1397-7-clabbe.montjoie@gmail.com \
--to=clabbe.montjoie@gmail.com \
--cc=arnd@arndb.de \
--cc=clemens@ladisch.de \
--cc=gregkh@linuxfoundation.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
all inboxes | Powered by JetHome®