public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CFT] more kdev_t-ectomy
Date: Sun, 20 Apr 2003 17:15:53 -0700	[thread overview]
Message-ID: <3EA33839.4050302@zytor.com> (raw)
In-Reply-To: <UTC200304202356.h3KNuYK14756.aeb@smtp.cwi.nl>

Andries.Brouwer@cwi.nl wrote:
> 
> It doesnt matter much. I would not have introduced kdev_t just
> for slightly more efficient dev_t handling. But we have it already.
> It seems meaningless to go and replace it by something more awkward
> and less efficient.
> 

It isn't, though, if it makes things cleaner and avoids double conversions.

> [But should anyone want: globally s/kdev_t/dev_t/ and a small edit
> of kdev_t.h suffices.]
> 
>     We do need a dev32_t for NFSv2 et al, though.
> 
> I don't know why.

So we can have (k)dev_t_to_dev32() for NFSv2 et al, which only allows 
for 32 bits in device numbers.  This is 12:20 <-> 32:32 conversions.

	-hpa



  reply	other threads:[~2003-04-21  0:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-20 23:56 [CFT] more kdev_t-ectomy Andries.Brouwer
2003-04-21  0:15 ` H. Peter Anvin [this message]
2003-04-21  0:35 ` viro
  -- strict thread matches above, loose matches on Subject: below --
2003-04-21  1:32 Andries.Brouwer
2003-04-21  3:54 ` H. Peter Anvin
2003-04-20 21:58 Andries.Brouwer
2003-04-20 22:35 ` viro
2003-04-20 21:17 Andries.Brouwer
2003-04-20 21:26 ` viro
2003-04-20 13:31 viro
2003-04-20 15:26 ` Muli Ben-Yehuda
2003-04-20 16:00 ` Andries Brouwer
2003-04-20 19:24   ` viro
2003-04-20 21:10   ` H. Peter Anvin

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=3EA33839.4050302@zytor.com \
    --to=hpa@zytor.com \
    --cc=Andries.Brouwer@cwi.nl \
    --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