From: Andries Brouwer <aebr@win.tue.nl>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] print_dev_t for 2.6.0-test1-mm
Date: Fri, 18 Jul 2003 02:04:44 +0200 [thread overview]
Message-ID: <20030718020444.A2612@pclin040.win.tue.nl> (raw)
In-Reply-To: <bf7clr$ang$1@news.cistron.nl>; from miquels@cistron.nl on Thu, Jul 17, 2003 at 11:49:15PM +0000
On Thu, Jul 17, 2003 at 11:49:15PM +0000, Miquel van Smoorenburg wrote:
> But why do you need a 32bit interface to the kernel when a
> 32:32 interface exists? Userland can translate 32 bit major/minor
> into 32:32 to the kernel, if a 64 bits syscall exists.
I? A 32bit interface to the kernel? Why do you think I want one?
The discussion has become too long, and people react to single
sentences in a reply instead of reading the thread.
[This started when I answered Andrew and wrote about a dev_t:
8+8 when 16-bit, otherwise 16+16 when 32-bit, otherwise 32+32.
Look: no kernel involved. No interface involved.
This structure is defined by <sys/sysmacros.h>.]
next prev parent reply other threads:[~2003-07-17 23:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 18:46 [PATCH] print_dev_t for 2.6.0-test1-mm Greg KH
2003-07-16 20:09 ` Andrew Morton
2003-07-16 21:02 ` Greg KH
2003-07-16 21:13 ` Andrew Morton
2003-07-16 21:34 ` Andries Brouwer
2003-07-16 21:39 ` Andrew Morton
2003-07-16 22:10 ` H. Peter Anvin
2003-07-16 22:20 ` Andries Brouwer
2003-07-16 22:21 ` Andrew Morton
2003-07-16 23:44 ` Andries Brouwer
2003-07-16 23:49 ` Andrew Morton
2003-07-17 8:27 ` Joel Becker
2003-07-17 8:47 ` Roman Zippel
2003-07-17 9:15 ` Joel Becker
2003-07-17 9:24 ` Andrew Morton
2003-07-17 10:10 ` Trond Myklebust
2003-07-17 11:46 ` Andries Brouwer
2003-07-17 11:52 ` Alan Cox
2003-07-17 10:26 ` Andries Brouwer
2003-07-17 10:46 ` Miquel van Smoorenburg
2003-07-17 11:19 ` Andries Brouwer
2003-07-17 11:46 ` Miquel van Smoorenburg
2003-07-17 21:55 ` Andrew Morton
2003-07-17 22:24 ` Andries Brouwer
2003-07-17 22:43 ` Joel Becker
2003-07-17 23:11 ` Andries Brouwer
2003-07-17 23:49 ` Miquel van Smoorenburg
2003-07-18 0:04 ` Andries Brouwer [this message]
2003-07-18 0:04 ` Joel Becker
2003-07-18 1:05 ` Andries Brouwer
2003-07-18 8:06 ` Joel Becker
2003-07-17 3:00 ` H. Peter Anvin
[not found] ` <200307170300.UAA24096@cesium.transmeta.com>
2003-07-17 10:43 ` Andries Brouwer
2003-07-20 14:33 ` H. Peter Anvin
2003-07-16 21:36 ` Greg KH
2003-07-16 22:00 ` Andrew Morton
2003-07-16 22:11 ` what's left for 64 bit dev_t Greg KH
2003-07-16 22:19 ` Andrew Morton
2003-07-16 22:48 ` Greg KH
2003-07-17 3:02 ` H. Peter Anvin
2003-07-17 13:59 ` Andries Brouwer
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=20030718020444.A2612@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
/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).