All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andries.Brouwer@cwi.nl, akpm@digeo.com,
	andrey@eccentric.mae.cornell.edu, linux-kernel@vger.kernel.org,
	torvalds@transmeta.com
Subject: Re: major/minor split
Date: Thu, 20 Mar 2003 13:47:41 -0800	[thread overview]
Message-ID: <20030320214740.GP2835@ca-server1.us.oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303202146100.12110-100000@serv>

On Thu, Mar 20, 2003 at 10:00:48PM +0100, Roman Zippel wrote:
> There is a point I'd like to get clear: where should the 16bit<->32bit 
> dev_t conversion happen?
> I think any software that cares about this should be safe by now. That 
> leaves us with on-disk and on-wire formats and IMO only at these places a 
> conversion should happen.

	Actually, no.  mknod(8), ls(1), and friends still assume struct
stat with u16.

Joel

-- 

"Every new beginning comes from some other beginning's end."

Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

  reply	other threads:[~2003-03-20 21:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 21:40 major/minor split Andries.Brouwer
2003-03-20 21:00 ` Roman Zippel
2003-03-20 21:47   ` Joel Becker [this message]
2003-03-20 22:03     ` Joel Becker
  -- strict thread matches above, loose matches on Subject: below --
2003-03-20 22:24 Andries.Brouwer
2003-03-20 23:23 ` Roman Zippel
2003-03-21  0:04   ` H. Peter Anvin
2003-03-20 23:52 ` H. Peter Anvin
2003-03-21  7:35 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=20030320214740.GP2835@ca-server1.us.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=akpm@digeo.com \
    --cc=andrey@eccentric.mae.cornell.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.