linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajesh Kumbhakar <sssraj.sssraj@gmail.com>
To: gregkh@linuxfoundation.org, sfr@canb.auug.org.au
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Rajesh Kumbhakar <sssraj.sssraj@gmail.com>
Subject: [PATCH v2] staging: wimax: i2400m: add space before open parenthesis
Date: Sat, 20 Feb 2021 05:46:52 -0800	[thread overview]
Message-ID: <20210220134652.16127-1-sssraj.sssraj@gmail.com> (raw)
In-Reply-To: <20210220104816.13263-1-sssraj.sssraj@gmail.com>

netdev.c

fixing style ERROR: space required before the open parenthesis '('

Signed-off-by: Rajesh Kumbhakar <sssraj.sssraj@gmail.com>
---
Changes in v2:
	- Removed filename from commit message.

 drivers/staging/wimax/i2400m/netdev.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/wimax/i2400m/netdev.c b/drivers/staging/wimax/i2400m/netdev.c
index cd06eaf75e8b..5b53e59084c8 100644
--- a/drivers/staging/wimax/i2400m/netdev.c
+++ b/drivers/staging/wimax/i2400m/netdev.c
@@ -523,7 +523,7 @@ void i2400m_net_erx(struct i2400m *i2400m, struct sk_buff *skb,
 
 	d_fnstart(2, dev, "(i2400m %p skb %p [%u] cs %d)\n",
 		  i2400m, skb, skb->len, cs);
-	switch(cs) {
+	switch (cs) {
 	case I2400M_CS_IPV4_0:
 	case I2400M_CS_IPV4:
 		i2400m_rx_fake_eth_header(i2400m->wimax_dev.net_dev,
-- 
2.25.1


  parent reply	other threads:[~2021-02-20 13:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 10:48 [PATCH] staging: wimax: i2400m: add space before open parenthesis Rajesh Kumbhakar
2021-02-20 11:12 ` Greg KH
2021-02-20 12:28   ` RajMAIN
2021-02-20 12:42     ` Greg KH
2021-02-20 13:46 ` Rajesh Kumbhakar [this message]
2021-02-21 13:06   ` [PATCH v2] " Greg KH
2021-02-21 13:23     ` Rajesh Kumbhakar
2021-02-21 13:39   ` [PATCH v3] " Rajesh Kumbhakar

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=20210220134652.16127-1-sssraj.sssraj@gmail.com \
    --to=sssraj.sssraj@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).