All of lore.kernel.org
 help / color / mirror / Atom feed
From: Debleena Sen <idebleenasen@gmail.com>
To: gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com
Cc: Debleena Sen <idebleenasen@gmail.com>
Subject: [PATCH v3] Staging: pi433: Fix line over 80 characters issue
Date: Sat,  2 Mar 2019 23:46:48 -0800	[thread overview]
Message-ID: <1551599208-3301-1-git-send-email-idebleenasen@gmail.com> (raw)

This patch re-formats the code to remove the checkpatch.pl warning(on
line no. 566):
WARNING: line over 80 characters

Signed-off-by: Debleena Sen <idebleenasen@gmail.com>
---
 drivers/staging/pi433/rf69.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/staging/pi433/rf69.c b/drivers/staging/pi433/rf69.c
index e19b9ce..0c189a7 100644
--- a/drivers/staging/pi433/rf69.c
+++ b/drivers/staging/pi433/rf69.c
@@ -563,7 +563,8 @@ bool rf69_get_flag(struct spi_device *spi, enum flag flag)
 {
 	switch (flag) {
 	case mode_switch_completed:
-		return (rf69_read_reg(spi, REG_IRQFLAGS1) & MASK_IRQFLAGS1_MODE_READY);
+		return (rf69_read_reg(spi, REG_IRQFLAGS1) &
+			MASK_IRQFLAGS1_MODE_READY);
 	case ready_to_receive:
 		return (rf69_read_reg(spi, REG_IRQFLAGS1) & MASK_IRQFLAGS1_RX_READY);
 	case ready_to_send:
-- 
2.7.4



             reply	other threads:[~2019-03-03  7:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-03  7:46 Debleena Sen [this message]
2019-03-03  7:56 ` [Outreachy kernel] [PATCH v3] Staging: pi433: Fix line over 80 characters issue Julia Lawall
2019-03-03  8:40   ` idebleenasen
2019-03-03  9:46     ` Julia Lawall
2019-03-03  9:51       ` idebleenasen
  -- strict thread matches above, loose matches on Subject: below --
2019-03-04 17:34 Debleena Sen
2019-03-04 19:01 ` Greg KH
2019-03-04 19:30   ` Debleena Sen
2019-03-05  7:03     ` 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=1551599208-3301-1-git-send-email-idebleenasen@gmail.com \
    --to=idebleenasen@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.