Re: [PATCH 0/5] new dasd ioctl patchkit

Christoph Hellwig wrote:
> As long as we backout the bogus eer
> patch before 2.6.16 all the cleanups and even the eckd ioctl fix
> can wait.  But don't put this crappy interface into 1.6.16 and thus
> SLES10 so that applications start to rely on it.
ACK: Given that a) both Horst and Christoph think the ioctl interface
needs cleanup but proposed cleanup interfers with existing
functionality (cmb), and b) later cleanup would change the
user-interface of eer, we should rush neither the ioctl change nor
eer into .16 until the maintainer is back afaics.

Carsten
-- 

Carsten Otte
IBM Linux technology center
ARCH=s390
-
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/

---

• Follow-Ups:
  • Re: [PATCH 0/5] new dasd ioctl patchkit
    • From: Andrew Morton <[email protected]>

• References:
  • Re: [PATCH 0/5] new dasd ioctl patchkit
    • From: Horst Hummel <[email protected]>
  • Re: [PATCH 0/5] new dasd ioctl patchkit
    • From: Christoph Hellwig <[email protected]>

• Prev by Date: Re: 2.6.16-rc3: more regressions
• Next by Date: [PATCH] remove VM_DONTCOPY bogosities
• Previous by thread: Re: [PATCH 0/5] new dasd ioctl patchkit
• Next by thread: Re: [PATCH 0/5] new dasd ioctl patchkit
• 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]