linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 4/4] sd: misc checkpatch.pl fixes
Date: Wed, 29 Apr 2009 22:46:12 +0200	[thread overview]
Message-ID: <200904292246.12746.bzolnier@gmail.com> (raw)
In-Reply-To: <1241036726.3369.63.camel@mulgrave.int.hansenpartnership.com>

On Wednesday 29 April 2009 22:25:26 James Bottomley wrote:
> On Wed, 2009-04-29 at 22:09 +0200, Bartlomiej Zolnierkiewicz wrote:
> > Fix
> > 
> > 	ERROR: trailing whitespace
> > 	ERROR: code indent should use tabs where possible
> > 	WARNING: line over 80 characters
> > 	WARNING: braces {} are not necessary for single statement blocks
> > 	ERROR: switch and case should be at the same indent
> > 	ERROR: space required before the open parenthesis '('
> > 
> > issues detected by checkpatch.pl.
> > 
> > While at it:
> > - remove superfluous 'ret' local variable in sd_compat_ioctl()
> 
> I'd really rather not encourage pure whitespace fixing patches in
> SCSI ... we already know there's a lot of non conforming problems from a
> crufty code base ... at one patch per file it would take about 500
> patches and several thousand lines of review.

Well, we could at least fix the core code -- which means a lot less than
500 files...  However I see your point and I have no problem with keeping
the patch locally until it is more useful or you change your mind.

Thanks,
Bart

      reply	other threads:[~2009-04-29 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 20:09 [PATCH 4/4] sd: misc checkpatch.pl fixes Bartlomiej Zolnierkiewicz
2009-04-29 20:25 ` James Bottomley
2009-04-29 20:46   ` Bartlomiej Zolnierkiewicz [this message]

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=200904292246.12746.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    /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).