Re: [PATCH 13/25] loop: move ioctl32 code to loop.c

On Sat, Nov 05, 2005 at 05:27:03PM +0100, Arnd Bergmann wrote:
> The loop device driver is the only user of its ioctl
> commands, so we can move the conversion handlers
> for 32 bit emulation into the driver itself.
> 
> This patch just moves over the function, it would
> probably be a good idea to get rid of get_fs/set_fs
> calls here by integrating better with the driver.

Yes.  just moving over is pointless.  for things like loop where
there's just one driver implementing the api moving it there does
make sense, but please bring the compat layer up to standards first.

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

---

• References:
  • [PATCH 13/25] loop: move ioctl32 code to loop.c
    • From: Arnd Bergmann <[email protected]>

• Prev by Date: Re: 2.6.14-mm1
• Next by Date: Re: [PATCH 17/25] vfat: move ioctl32 code to fs/fat/dir.c
• Previous by thread: [PATCH 13/25] loop: move ioctl32 code to loop.c
• Next by thread: [PATCH 02/25] net: move socket ioctl32 to net/compat.c
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]