mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andries.Brouwer@cwi.nl
Cc: akpm@digeo.com, linux-kernel@vger.kernel.org, zippel@linux-m68k.org
Subject: Re: [PATCH 1/3] revert register_chrdev_region change
Date: Mon, 24 Mar 2003 19:10:57 +0000	[thread overview]
Message-ID: <20030324191057.B23239@infradead.org> (raw)
In-Reply-To: <UTC200303241907.h2OJ75619479.aeb@smtp.cwi.nl>; from Andries.Brouwer@cwi.nl on Mon, Mar 24, 2003 at 08:07:05PM +0100

On Mon, Mar 24, 2003 at 08:07:05PM +0100, Andries.Brouwer@cwi.nl wrote:
> Yes, it is more elegant to register one or more ranges.
> (But ranges of what? Ranges in dev_t space? Or in kdev_t space?

In dev_t space.

> Here you see one reason to wait a little until dev_t/kdev_t
> stuff has settled.)

I guess basically everyone will disagree with you on making kdev_t
a different representation.  This will end up as messy as the
internal/external dev_t stuff on some of the SVR4 ports.


  reply	other threads:[~2003-03-24 18:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 19:07 Andries.Brouwer
2003-03-24 19:10 ` Christoph Hellwig [this message]
2003-03-24 20:55 ` Roman Zippel
  -- strict thread matches above, loose matches on Subject: below --
2003-03-24 22:40 Andries.Brouwer
2003-03-24 22:52 ` Roman Zippel
2003-03-24 22:06 Andries.Brouwer
2003-03-24 22:28 ` Roman Zippel
2003-03-24 20:34 Andries.Brouwer
2003-03-24 20:39 ` Christoph Hellwig
2003-03-23 23:25 Roman Zippel
2003-03-24 14:25 ` Andries Brouwer
2003-03-24 14:43   ` Roman Zippel
2003-03-24 15:04   ` Christoph Hellwig
2003-03-24 16:09     ` Roman Zippel

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=20030324191057.B23239@infradead.org \
    --to=hch@infradead.org \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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®