All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chetan Sethi <cpsethi369@gmail.com>
To: gregkh@linuxfoundation.org
Cc: wsa@the-dreams.de, bhumirks@gmail.com, mattkilgore12@gmail.com,
	weiyongjun1@huawei.com, shiva@exdev.nl, punitvara@gmail.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Chetan Sethi <cpsethi369@gmail.com>
Subject: [PATCH v3 1/6] staging: ks7010: fixed warning of avoiding line over 80 characters
Date: Fri, 17 Feb 2017 18:46:19 +0900	[thread overview]
Message-ID: <1487324779-28998-1-git-send-email-cpsethi369@gmail.com> (raw)
In-Reply-To: <20170216182800.GA30761@kroah.com>

This is patch 01 to ks_wlan.h file in order to fix warning of line over
80 characters, as issued by checkpatch.pl

Signed-off-by: Chetan Sethi <cpsethi369@gmail.com>
---
v2:
 - split multiple changes across different patches
v3:
 - mentioned patch revision in subject

 drivers/staging/ks7010/ks_wlan.h | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/drivers/staging/ks7010/ks_wlan.h b/drivers/staging/ks7010/ks_wlan.h
index 9ab80e1..668202d 100644
--- a/drivers/staging/ks7010/ks_wlan.h
+++ b/drivers/staging/ks7010/ks_wlan.h
@@ -18,10 +18,10 @@
 #include <linux/kernel.h>
 #include <linux/module.h>
 
-#include <linux/spinlock.h>	/* spinlock_t                                   */
-#include <linux/sched.h>	/* wait_queue_head_t                            */
-#include <linux/types.h>	/* pid_t                                        */
-#include <linux/netdevice.h>	/* struct net_device_stats,  struct sk_buff     */
+#include <linux/spinlock.h>	/* spinlock_t */
+#include <linux/sched.h>	/* wait_queue_head_t */
+#include <linux/types.h>	/* pid_t */
+#include <linux/netdevice.h>	/* struct net_device_stats,  struct sk_buff */
 #include <linux/etherdevice.h>
 #include <linux/wireless.h>
 #include <linux/atomic.h>	/* struct atomic_t */
@@ -36,7 +36,8 @@
 
 #ifdef KS_WLAN_DEBUG
 #define DPRINTK(n, fmt, args...) \
-                 if (KS_WLAN_DEBUG > (n)) printk(KERN_NOTICE "%s: "fmt, __FUNCTION__, ## args)
+                 if (KS_WLAN_DEBUG > (n)) \
+			printk(KERN_NOTICE "%s: "fmt, __FUNCTION__, ## args)
 #else
 #define DPRINTK(n, fmt, args...)
 #endif
-- 
2.7.4

       reply	other threads:[~2017-02-17  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170216182800.GA30761@kroah.com>
2017-02-17  9:46 ` Chetan Sethi [this message]
2017-02-17  9:47   ` [PATCH v3 2/6] staging: ks7010: fix coding style issue of enclosing complex macro value in parentheses Chetan Sethi
2017-02-24 17:07     ` Greg KH
2017-02-17  9:48   ` [PATCH v3 3/6] staging: ks7010: fix coding style issue of using tabs instead of spaces Chetan Sethi
2017-02-17  9:48   ` [PATCH v3 4/6] drivers: staging: fix coding style issue of using pr_notice instead of printk Chetan Sethi
2017-02-24 17:47     ` Greg KH
2017-02-17  9:49   ` [PATCH v3 5/6] drivers: staging: fix coding style issue of using __func__ instead of __FUNCTION__ Chetan Sethi
2017-02-17  9:49   ` [PATCH v3 6/6] drivers: staging: fix coding style issue of aligning comments properly Chetan Sethi

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=1487324779-28998-1-git-send-email-cpsethi369@gmail.com \
    --to=cpsethi369@gmail.com \
    --cc=bhumirks@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattkilgore12@gmail.com \
    --cc=punitvara@gmail.com \
    --cc=shiva@exdev.nl \
    --cc=weiyongjun1@huawei.com \
    --cc=wsa@the-dreams.de \
    /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.