Re: [PATCH 1/3] VFS: apply coding standards to fs/ioctl.c

2007-10-30 Thread Christoph Hellwig
On Sun, Oct 28, 2007 at 02:05:16PM -0400, Erez Zadok wrote: Sure. I assume you mean an internal function to encapsulate the entire case statement's code, one for each of the FIO* cases. Yes. - To unsubscribe from this list: send the line unsubscribe linux-fsdevel in the body of a message to

Re: [PATCH 1/3] VFS: apply coding standards to fs/ioctl.c

2007-10-30 Thread Christoph Hellwig
On Sun, Oct 28, 2007 at 07:57:47PM -0700, Daniel Phillips wrote: On 10/28/07, Christoph Hellwig [EMAIL PROTECTED] wrote: While you're at it, it's probably worth splitting this out into a small helper function. Why? Is the same pattern called from more than one place? Becauase it's a lot

Re: [PATCH 1/3] VFS: apply coding standards to fs/ioctl.c

2007-10-28 Thread Christoph Hellwig
Nice, I always hated these double-indented switch statements. + case FIBMAP: + { + struct address_space *mapping = filp-f_mapping; + int res; + /* do we support this mess? */ + if (!mapping-a_ops-bmap) + return

Re: [PATCH 1/3] VFS: apply coding standards to fs/ioctl.c

2007-10-28 Thread Erez Zadok
In message [EMAIL PROTECTED], Christoph Hellwig writes: Nice, I always hated these double-indented switch statements. + case FIBMAP: + { + struct address_space *mapping = filp-f_mapping; + int res; + /* do we support this mess? */ + if

Re: [PATCH 1/3] VFS: apply coding standards to fs/ioctl.c

2007-10-28 Thread Daniel Phillips
On 10/28/07, Christoph Hellwig [EMAIL PROTECTED] wrote: While you're at it, it's probably worth splitting this out into a small helper function. Why? Is the same pattern called from more than one place? Regards, Daniel - To unsubscribe from this list: send the line unsubscribe linux-fsdevel