Messages in this thread | | | Date | Thu, 16 Feb 2006 06:46:44 +0100 | From | Heiko Carstens <> | Subject | Re: [PATCH 0/5] new dasd ioctl patchkit |
| |
> > > 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. > > > > I don't have a patch in hand to purely back out the eer modeule. What I > have is > > dasd-cleanup-dasd_ioctl.patch > dasd-cleanup-dasd_ioctl-fix.patch > dasd-add-per-disciple-ioctl-method.patch > dasd-merge-dasd_cmd-into-dasd_mod.patch > dasd-backout-dasd_eer-module.patch > dasd-kill-dynamic-ioctl-registration.patch > > So what do we do?
Looks like people still haven't agreed. If they _finally_ agree on something and the result is that the eer should be backed out, I will send that patch. Sorry... I'm just the stupid patch monkey here.
Heiko - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |