From: Andreas Schwab <schwab@suse.de>
To: Ben LaHaise <bcrl@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [resend PATCH] reserve BLKGETSIZE64 ioctl
Date: 03 Sep 2001 18:02:38 +0200 [thread overview]
Message-ID: <jezo8cw9cx.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0109031119400.1610-100000@toomuch.toronto.redhat.com>
In-Reply-To: <Pine.LNX.4.33.0109031119400.1610-100000@toomuch.toronto.redhat.com> (Ben LaHaise's message of "Mon, 3 Sep 2001 11:21:39 -0400 (EDT)")
Ben LaHaise <bcrl@redhat.com> writes:
|> Hello,
|>
|> Is there any problem with the patch below for reserving a 64 bit get block
|> device size ioctl?
Yes.
|> diff -urN v2.4.10-pre4/include/linux/fs.h work/include/linux/fs.h
|> --- v2.4.10-pre4/include/linux/fs.h Mon Sep 3 11:04:39 2001
|> +++ work/include/linux/fs.h Mon Sep 3 11:18:44 2001
|> @@ -182,7 +182,8 @@
|> /* This was here just to show that the number is taken -
|> probably all these _IO(0x12,*) ioctls should be moved to blkpg.h. */
|> #endif
|> -/* A jump here: 108-111 have been used for various private purposes. */
|> +/* A jump here: 108,109,111 have been used for various private purposes. */
|> +#define BLKBSZGET _IOR(0x12,110,sizeof(u64))
|> #define BLKBSZGET _IOR(0x12,112,sizeof(int))
^^^^^^^^^
Conflicting definitions.
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
next prev parent reply other threads:[~2001-09-03 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 15:21 Ben LaHaise
2001-09-03 16:02 ` Andreas Schwab [this message]
[not found] <Pine.LNX.4.33.0109031119400.1610-100000@toomuch.toronto.re dhat.com>
2001-09-03 15:40 ` Anton Altaparmakov
2001-09-03 20:57 Andries.Brouwer
2001-09-04 1:09 ` Ben LaHaise
2001-09-04 13:50 Andries.Brouwer
2001-09-04 20:54 ` Ben LaHaise
2001-09-04 21:43 Andries.Brouwer
2001-09-04 22:27 ` 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=jezo8cw9cx.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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®