mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
To: <linux-kernel@vger.kernel.org>, <linux-parport@lists.infradead.org>
Cc: <sudipm.mukherjee@gmail.com>, <sudip.mukherjee@codethink.co.uk>,
	<akpm@linux-foundation.org>,
	Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
Subject: [PATCH 0/5] parport: cleanup several checkpatch issues
Date: Mon, 17 Jul 2017 17:36:57 +0100	[thread overview]
Message-ID: <20170717163702.17427-1-palminha@synopsys.com> (raw)

cleanup 6 type of checkpatch issues, each type per patch:
  - trailing statements should be on next line
  - space prohibited between function name and open parenthesis '('
  - do not initialise statics to 0 / NULL
  - that open brace { should be on the previous line
  - braces {} are not necessary for any arm of this statement

The patchset was based on linux next, tag next-20170714

Carlos Palminha (5):
  parport: add newline to trailing statements
  parport: cleanup prohibited space after functions name
  parport: cleanup statics initialization to NULL or 0
  parport: move open braces to the same line
  parport: remove unnecessary braces

 drivers/parport/daisy.c          |  12 +-
 drivers/parport/ieee1284.c       | 267 +++++++++++++++---------------
 drivers/parport/ieee1284_ops.c   | 345 ++++++++++++++++++++-------------------
 drivers/parport/parport_atari.c  |   6 +-
 drivers/parport/parport_cs.c     |   4 +-
 drivers/parport/parport_gsc.c    |  78 ++++-----
 drivers/parport/parport_ip32.c   |   2 +-
 drivers/parport/parport_mfc3.c   |   4 +-
 drivers/parport/parport_pc.c     |   3 +-
 drivers/parport/parport_serial.c |  52 +++---
 drivers/parport/parport_sunbpp.c |  29 ++--
 drivers/parport/probe.c          |  46 +++---
 drivers/parport/procfs.c         |  28 ++--
 13 files changed, 438 insertions(+), 438 deletions(-)

-- 
2.11.0

             reply	other threads:[~2017-07-17 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 16:36 Carlos Palminha [this message]
2017-07-17 16:36 ` [PATCH 1/5] parport: add newline to trailing statements Carlos Palminha
2017-08-07 20:42   ` Sudip Mukherjee
2017-07-17 16:36 ` [PATCH 2/5] parport: cleanup prohibited space after functions name Carlos Palminha
2017-08-07 20:49   ` Sudip Mukherjee
2017-07-17 16:37 ` [PATCH 3/5] parport: cleanup statics initialization to NULL or 0 Carlos Palminha
2017-07-17 16:37 ` [PATCH 4/5] parport: move open braces to the same line Carlos Palminha
2017-07-17 16:40 ` [PATCH 5/5] parport: remove unnecessary braces Carlos Palminha

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=20170717163702.17427-1-palminha@synopsys.com \
    --to=carlos.palminha@synopsys.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parport@lists.infradead.org \
    --cc=sudip.mukherjee@codethink.co.uk \
    --cc=sudipm.mukherjee@gmail.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 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®