public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Joe Perches <joe@perches.com>
Cc: David Miller <davem@davemloft.net>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/block/floppy.c: stylistic cleanups
Date: Tue, 1 Dec 2009 08:45:50 -0800	[thread overview]
Message-ID: <20091201084550.586a728b@nehalam> (raw)
In-Reply-To: <1259640820.13592.37.camel@Joe-Laptop.home>

On Mon, 30 Nov 2009 20:13:40 -0800
Joe Perches <joe@perches.com> wrote:

> On Mon, 2009-11-30 at 09:28 -0800, Stephen Hemminger wrote:
> > Rather than playing with the dangling operator format which seems to be a coding
> > style that only David cares about. Why not go through and fix the really ugly old
> > drivers that need it. For a good horror experience, go look at the floppy driver.
> 
> Just for you Stephen, here's a cleaned up version.
> Now to see if it gets applied, which I rather doubt.
> 
> Changes:
> 
> Removed macro definitions and uses of
> 	IN, OUT, LAST_OUT, CLEARSTRUCT, and CHECK_RESET
> Used C99 initializers
> Removed assigns from if statements
> Converted printks without KERN_ levels to pr_info and pr_cont
> Removed unnecessary braces
> Used print_hex_dump
> Moved leading logical tests to end of previous line
> Surrounded still ugly CALL and ECALL macro with do {} while (0)
> 
> Checkpatch complaints before:
> total: 393 errors, 132 warnings, 4647 lines checked
> 
> after:
> total: 1 errors, 11 warnings, 5352 lines checked
> 
> Compile tested only, x86 allyesconfig
> 
> Signed-off-by: Joe Perches <joe@perches.com>

I have a fix (to get rid of Buffer I/O error when testing for drive present),
so I'll put your cleanup in first.


-- 

  reply	other threads:[~2009-12-01 16:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1259001504.16503.79.camel@Joe-Laptop.home>
     [not found] ` <20091123.104130.117837098.davem@davemloft.net>
     [not found]   ` <1259528449.29779.194.camel@Joe-Laptop.home>
     [not found]     ` <20091129.165557.84377714.davem@davemloft.net>
     [not found]       ` <20091130092837.4998f961@nehalam>
2009-12-01  4:13         ` [PATCH] drivers/block/floppy.c: stylistic cleanups Joe Perches
2009-12-01 16:45           ` Stephen Hemminger [this message]
2009-12-01 19:09             ` Bartlomiej Zolnierkiewicz
2009-12-01 17:36           ` Marcin Slusarz
2009-12-01 17:46             ` Joe Perches
2009-12-01 18:39           ` Bartlomiej Zolnierkiewicz
     [not found]       ` <1259863101.22783.63.camel@Joe-Laptop.home>
     [not found]         ` <4B190A29.5080905@myri.com>
     [not found]           ` <1259947271.22783.120.camel@Joe-Laptop.home>
2009-12-05 12:43             ` [PATCH net-next-2.6] drivers/net: Move && and || to end of previous line William Allen Simpson
2009-12-05 17:50               ` Joe Perches
2009-12-05 22:05                 ` Jarek Poplawski
2009-12-06  3:36                 ` William Allen Simpson
2009-12-05 22:21               ` David Miller
2009-12-06  3:00                 ` William Allen Simpson
2009-12-06 17:01                   ` Jonathan Corbet

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=20091201084550.586a728b@nehalam \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --cc=linux-kernel@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