From: "David S. Miller" <davem@redhat.com>
To: bcrl@redhat.com
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blkgetsize64 ioctl
Date: Wed, 29 Aug 2001 17:03:15 -0700 (PDT) [thread overview]
Message-ID: <20010829.170315.28787631.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108291840310.28439-100000@toomuch.toronto.redhat.com>
In-Reply-To: <Pine.LNX.4.33.0108291840310.28439-100000@toomuch.toronto.redhat.com>
From: Ben LaHaise <bcrl@redhat.com>
Date: Wed, 29 Aug 2001 18:45:20 -0400 (EDT)
The patch below reserves an ioctl for getting the size in blocks of a
device as a long long instead of long as the old ioctl did. The patch for
this to e2fsprogs sneaked in a bit too early. There is a conflict with
the ia64 get/set sector ioctls, but I that's less common than e2fsprogs.
Any problems with using "u64" or some other more strictly portable
type? "long long" and other non-fixed sized types cause grief for
many dual-API platforms.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-08-30 0:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 22:45 [PATCH] blkgetsize64 ioctl Ben LaHaise
2001-08-30 0:03 ` David S. Miller [this message]
2001-08-30 0:16 ` Ben LaHaise
2001-08-30 11:57 Andries.Brouwer
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
2001-08-30 19:03 ` Alan Cox
2001-08-30 19:10 ` Michael E Brown
2001-08-30 19:18 ` Alan Cox
2001-08-31 1:15 Andries.Brouwer
2001-08-31 1:23 ` Alan Cox
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=20010829.170315.28787631.davem@redhat.com \
--to=davem@redhat.com \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).