From: Andrew Morton <akpm@digeo.com>
To: Joe Thornber <joe@fib011235813.fsnet.co.uk>
Cc: Andries.Brouwer@cwi.nl, corryk@us.ibm.com,
linux-kernel@vger.kernel.org, lvm-devel@sistina.com
Subject: Re: struct dm_ioctl
Date: Wed, 26 Mar 2003 16:49:38 -0800 [thread overview]
Message-ID: <20030326164938.6558a2c5.akpm@digeo.com> (raw)
In-Reply-To: <35A0ECE4-5F89-11D7-BBDF-000393CA5730@fib011235813.fsnet.co.uk>
Joe Thornber <joe@fib011235813.fsnet.co.uk> wrote:
>
>
> On Wednesday, March 26, 2003, at 11:27 AM, Andries.Brouwer@cwi.nl wrote:
>
> > One is struct dm_ioctl. Google tells me that it was
> > noticed already that it defined a broken interface,
> > and Kevin Corry submitted a patch against 2.5.51.
> > Today this has not been applied yet.
> >
> > What is the status? Should I resubmit that patch?
>
> The patch is queued, and should be merged very soon. The only reason I
> delayed was that I wanted to update both the 2.4 and 2.5 releases at
> the same time so that people can continue to switch back and forth
> between kernels. That said, I have left it too long, sorry.
Please send me a copy. I'd like to get all the required bits and pieces for
this conversion queued up in one place so we can actually look at it,
evaluate its impact and test it. The current process of creeping revelations
is quite confusing.
Also if userspace tools need upgrading please send me the URLs so I can make
people well aware of the upgrade requirements and process.
Thanks.
prev parent reply other threads:[~2003-03-26 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 11:27 Andries.Brouwer
2003-03-26 11:34 ` Christoph Hellwig
2003-03-26 12:48 ` Joe Thornber
2003-03-27 0:49 ` Andrew Morton [this message]
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=20030326164938.6558a2c5.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=corryk@us.ibm.com \
--cc=joe@fib011235813.fsnet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lvm-devel@sistina.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
all inboxes | Powered by JetHome®