All of lore.kernel.org
 help / color / mirror / Atom feed
From: sayli karnik <karniksayli1995@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: gregkh@linuxfoundation.org
Subject: [PATCH 0/6] staging: ks7010: ks7010_sdio.c: Fix multiple checkpatch warnings
Date: Thu, 15 Sep 2016 01:12:48 +0530	[thread overview]
Message-ID: <cover.1473877138.git.karniksayli1995@gmail.com> (raw)

This patchset fixes several checkpatch issues detected in the ks7010_sdio.c
file of the ks7010 driver.

sayli karnik (6):
  Use <linux/atomic.h> instead of <asm/atomic.h>
  Remove braces following single statement blocks
  Remove space after '(' and before ')'
  Remove unnecessary blank lines
  Remove the space after a type cast
  Remove the null check before kfree

 drivers/staging/ks7010/ks7010_sdio.c | 75 +++++++++++++++---------------------
 1 file changed, 32 insertions(+), 43 deletions(-)

-- 
2.7.4



             reply	other threads:[~2016-09-14 19:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 19:42 sayli karnik [this message]
2016-09-14 19:45 ` [PATCH 1/6] staging: ks7010: ks7010_sdio.c: Use <linux/atomic.h> instead of <asm/atomic.h> sayli karnik
2016-09-14 19:47 ` [PATCH 2/6] staging: ks7010: ks7010_sdio.c: Remove braces following single statement blocks sayli karnik
2016-09-14 19:48 ` [PATCH 3/6] staging: ks7010: ks7010_sdio.c: Remove space after '(' and before ')' sayli karnik
2016-09-14 19:49 ` [PATCH 4/6] staging: ks7010: ks7010_sdio.c: Remove unnecessary blank lines sayli karnik
2016-09-14 20:21   ` [Outreachy kernel] " Julia Lawall
2016-09-14 19:50 ` [PATCH 5/6] staging: ks7010: ks7010_sdio.c: Remove the space after a type cast sayli karnik
2016-09-14 20:20   ` [Outreachy kernel] " Julia Lawall
2016-09-14 19:51 ` [PATCH 6/6] staging: ks7010: ks7010_sdio.c: Remove the null check before kfree sayli karnik

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=cover.1473877138.git.karniksayli1995@gmail.com \
    --to=karniksayli1995@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.