From: Theodore Tso <tytso@mit.edu>
To: Ben LaHaise <bcrl@redhat.com>
Cc: Michael E Brown <michael_e_brown@dell.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blkgetsize64 ioctl
Date: Thu, 30 Aug 2001 14:51:55 -0400 [thread overview]
Message-ID: <20010830145155.A3114@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0108301150460.1213-100000@blap.linuxdev.us.dell.com> <Pine.LNX.4.33.0108301306300.12593-100000@toomuch.toronto.redhat.com>
In-Reply-To: <Pine.LNX.4.33.0108301306300.12593-100000@toomuch.toronto.redhat.com>; from bcrl@redhat.com on Thu, Aug 30, 2001 at 01:12:07PM -0400
On Thu, Aug 30, 2001 at 01:12:07PM -0400, Ben LaHaise wrote:
>
> No, that's not what's got me miffed. What is a problem here is that an
> obvious next to use ioctl number in a *CORE* kernel api was used without
> reserving it. AND PEOPLE SHIPPED IT! I for one don't go about shipping
> new ABIs without reserving at least a placeholder for it in the main
> kernel (or stating that the code is not bearing a fixed ABI). If the
> ioctl # was in the main kernel, this mess would never have happened even
> with the accidental shipping of the patch in e2fsprogs.
... and for my part, I included the patch in e2fsprogs because Ben
sent me the patch, saying that people would want to test it, and I
assumed he had already reserved the ioctl in the kernel. I should
have checked first....
- Ted
next prev parent reply other threads:[~2001-08-30 18:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 16:11 Michael E Brown
2001-08-30 16:25 ` Ben LaHaise
2001-08-30 16:44 ` Michael E Brown
2001-08-30 16:47 ` Ben LaHaise
2001-08-30 17:02 ` Michael E Brown
2001-08-30 17:12 ` Ben LaHaise
2001-08-30 17:34 ` Michael E Brown
2001-08-30 18:51 ` Theodore Tso [this message]
2001-08-30 19:03 ` Alan Cox
2001-08-30 19:10 ` Michael E Brown
2001-08-30 19:18 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-08-31 1:15 Andries.Brouwer
2001-08-31 1:23 ` Alan Cox
2001-08-30 11:57 Andries.Brouwer
2001-08-29 22:45 Ben LaHaise
2001-08-30 0:03 ` David S. Miller
2001-08-30 0:16 ` Ben LaHaise
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=20010830145155.A3114@thunk.org \
--to=tytso@mit.edu \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael_e_brown@dell.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®