mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Hoefler <michael.hoefler@studium.uni-erlangen.de>
To: michael.hoefler@studium.uni-erlangen.de
Cc: linux-kernel@i4.cs.fau.de,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Christoph Kohl <christoph.kohl@t-online.de>,
	Rupert Muchembled <rupert@rmuch.net>,
	Chad Williamson <chad@dahc.us>,
	devel@driverdev.osuosl.org (open list:STAGING SUBSYSTEM),
	linux-kernel@vger.kernel.org (open list)
Subject: [PATCHv2 0/3] staging: silicom: fix code styling according to checkpatch
Date: Fri, 20 Dec 2013 14:51:10 +0100	[thread overview]
Message-ID: <1387547475-7135-1-git-send-email-michael.hoefler@studium.uni-erlangen.de> (raw)

This patch series fixes most issues discovered by checkpatch. That includes
whitespaces, indentation, the wrong use of parenthesis and some more. Please
refer to the specific patch description to get more details.

Besides some minor issues not discovered by checkpatch are fixed. E.g. i moved some empty lines for a better readability and added missing braces.

This series does not perform functional changes to the code because i do not
have any hardware to test it.


Michael Hoefler (3):
  silicom: fix whitespace issues in bypass.c
  silicom: fix coding style issues in bypass.c
  silicom: remaining checkpatch issues in bypass.c

 drivers/staging/silicom/bypasslib/bypass.c | 158 ++++++++++++++++-------------
 1 file changed, 85 insertions(+), 73 deletions(-)

-- 
1.8.1.2


             reply	other threads:[~2013-12-20 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 13:51 Michael Hoefler [this message]
2013-12-20 13:51 ` [PATCHv2 1/3] silicom: fix whitespace issues in bypass.c Michael Hoefler
2013-12-20 15:06   ` Gokulnath A
2013-12-20 17:01     ` Greg Kroah-Hartman
2013-12-20 17:05       ` Gokulnath A
2013-12-20 13:51 ` [PATCHv2 2/3] silicom: fix coding style " Michael Hoefler
2013-12-20 13:51 ` [PATCHv2 3/3] silicom: remaining checkpatch " Michael Hoefler

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=1387547475-7135-1-git-send-email-michael.hoefler@studium.uni-erlangen.de \
    --to=michael.hoefler@studium.uni-erlangen.de \
    --cc=chad@dahc.us \
    --cc=christoph.kohl@t-online.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rupert@rmuch.net \
    /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

all inboxes | Powered by JetHome®