[PATCH 00/24] drivers/block/floppy.c cleanups

From: Joe Perches
Date: Thu Jan 21 2010 - 23:57:09 EST

Since Stephen Hemminger is a bit too busy to do much with this
I've broken up the first large patch into multiple pieces and
brought the rest up to current.

I dropped the c99 conversions because Bartlomiej Zolnierkiewicz

This applies against Linus' and -next.

Maybe somebody will decide it's useful.

Original submissions:

Joe Perches (24):
drivers/block/floppy.c: Convert some #include <asm/ to #include <linux/
drivers/block/floppy.c: #define space and column neatening
drivers/block/floppy.c: Use pr_<level>
drivers/block/floppy.c: Remove unnecessary braces
drivers/block/floppy.c: Remove used once CHECK_READY macro
drivers/block/floppy.c: Hoist assigns from if()s, neatening
drivers/block/floppy.c: Remove LAST_OUT macro
drivers/block/floppy.c: Comment neatening and remove naked ;
drivers/block/floppy.c: Remove CLEARSTRUCT macro, use memset
drivers/block/floppy.c: Indent a comment
drivers/block/floppy.c: Remove IN/OUT macros, indent switch/case
drivers/block/floppy.c: Remove a few spaces from function casts
drivers/block/floppy.c: Remove macro LOCK_FDC
drivers/block/floppy.c: Add debug_dcl(...) macro
drivers/block/floppy.c: Remove [U]CLEARF, [U]SETF, and [U]TESTF macros
drivers/block/floppy.c: Remove most uses of CALL and ECALL macros
drivers/block/floppy.c: remove [_]COPYIN [_]COPYOUT and ECALL macros
drivers/block/floppy.c: remove macros CALL, WAIT and IWAIT
drivers/block/floppy.c: convert int 1/0 to bool true/false
drivers/block/floppy.c: Move leading && and || to preceding line
drivers/block/floppy.c: remove #define DEVICE_NAME "floppy"
drivers/block/floppy.c: Convert int initialising to bool initialized
drivers/block/floppy.c: Add function is_ready_state
drivers/block/floppy.c: Remove unnecessary return and braces

drivers/block/floppy.c | 1219 ++++++++++++++++++++++++------------------------
1 files changed, 618 insertions(+), 601 deletions(-)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/