From: Andrew Morton <akpm@osdl.org>
To: carsteno@de.ibm.com
Cc: cotte@de.ibm.com, hch@lst.de, horst.hummel@de.ibm.com,
linux-kernel@vger.kernel.org, heicars2@de.ibm.com,
wein@de.ibm.com, mschwid2@de.ibm.com, ihno@suse.de
Subject: Re: [PATCH 0/5] new dasd ioctl patchkit
Date: Wed, 15 Feb 2006 12:03:43 -0800 [thread overview]
Message-ID: <20060215120343.1e4e8afe.akpm@osdl.org> (raw)
In-Reply-To: <43F3397B.3090207@de.ibm.com>
Carsten Otte <cotte@de.ibm.com> wrote:
>
> 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.
>
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?
next prev parent reply other threads:[~2006-02-15 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 16:53 [PATCH 0/5] new dasd ioctl patchkit Horst Hummel
2006-02-14 19:09 ` Christoph Hellwig
2006-02-15 14:23 ` Carsten Otte
2006-02-15 20:03 ` Andrew Morton [this message]
2006-02-16 5:46 ` Heiko Carstens
2006-02-15 21:14 ` Stefan Weinhuber
-- strict thread matches above, loose matches on Subject: below --
2006-02-12 17:38 Christoph Hellwig
2006-02-13 7:04 ` Heiko Carstens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060215120343.1e4e8afe.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=carsteno@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=hch@lst.de \
--cc=heicars2@de.ibm.com \
--cc=horst.hummel@de.ibm.com \
--cc=ihno@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mschwid2@de.ibm.com \
--cc=wein@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox