From: Chase Metzger <chasemetzger15@gmail.com>
To: gregkh@linuxfoundation.org
Cc: Chase Metzger <chasemetzger15@gmail.com>,
Marcus Wolf <linux@Wolf-Entwicklungen.de>,
Joseph Wright <rjosephwright@gmail.com>,
Colin Ian King <colin.king@canonical.com>,
Haneen Mohammed <hamohammed.sa@gmail.com>,
Elia Geretto <elia.f.geretto@gmail.com>,
Srishti Sharma <srishtishar@gmail.com>,
Xiangyang Zhang <xyz.sun.ok@gmail.com>,
Derek Robson <robsonde@gmail.com>,
Cihangir Akturk <cakturk@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] staging: pi433: pi433_if.c: fix if/else if and brace coding style issues
Date: Tue, 14 Nov 2017 12:03:51 -0800 [thread overview]
Message-ID: <20171114200357.4628-1-chasemetzger15@gmail.com> (raw)
Fix if/else if and braces in function DIO0_irq_handler to comply with
the kernel coding style.
Signed-off-by: Chase Metzger <chasemetzger15@gmail.com>
---
drivers/staging/pi433/pi433_if.c | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/pi433/pi433_if.c b/drivers/staging/pi433/pi433_if.c
index d946838450d4..dee70c47629c 100644
--- a/drivers/staging/pi433/pi433_if.c
+++ b/drivers/staging/pi433/pi433_if.c
@@ -133,19 +133,14 @@ static irqreturn_t DIO0_irq_handler(int irq, void *dev_id)
{
struct pi433_device *device = dev_id;
- if (device->irq_state[DIO0] == DIO_PacketSent)
- {
+ if (device->irq_state[DIO0] == DIO_PacketSent) {
device->free_in_fifo = FIFO_SIZE;
dev_dbg(device->dev, "DIO0 irq: Packet sent\n");
wake_up_interruptible(&device->fifo_wait_queue);
- }
- else if (device->irq_state[DIO0] == DIO_Rssi_DIO0)
- {
+ } else if (device->irq_state[DIO0] == DIO_Rssi_DIO0) {
dev_dbg(device->dev, "DIO0 irq: RSSI level over threshold\n");
wake_up_interruptible(&device->rx_wait_queue);
- }
- else if (device->irq_state[DIO0] == DIO_PayloadReady)
- {
+ } else if (device->irq_state[DIO0] == DIO_PayloadReady) {
dev_dbg(device->dev, "DIO0 irq: PayloadReady\n");
device->free_in_fifo = 0;
wake_up_interruptible(&device->fifo_wait_queue);
--
2.11.0
next reply other threads:[~2017-11-14 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 20:03 Chase Metzger [this message]
2017-11-28 13:01 ` Greg KH
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=20171114200357.4628-1-chasemetzger15@gmail.com \
--to=chasemetzger15@gmail.com \
--cc=cakturk@gmail.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=elia.f.geretto@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@Wolf-Entwicklungen.de \
--cc=rjosephwright@gmail.com \
--cc=robsonde@gmail.com \
--cc=srishtishar@gmail.com \
--cc=xyz.sun.ok@gmail.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
Powered by JetHome