linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: device-mapper development <dm-devel@redhat.com>,
	"Alan D. Brunelle" <Alan.Brunelle@hp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [dm-devel] Re: Problem w/ CONFIG_DEBUG_BLOCK_EXT_DEVT
Date: Tue, 02 Sep 2008 14:23:13 +0200	[thread overview]
Message-ID: <48BD3031.3090905@kernel.org> (raw)
In-Reply-To: <20080902122006.GN15123@agk.fab.redhat.com>

Alasdair G Kergon wrote:
> On Tue, Sep 02, 2008 at 01:06:24PM +0200, Tejun Heo wrote:
>> Well, dev_t is 32bits and MINORBITS is 20.  So, major 12 bits, minor 20
>> bits, so 4 characters for major, 7 characters for minor.
>  
> Upstream libdevmapper CVS patched - will appear in next release (1.02.28).

Alright, thanks.  What about the /proc/devices one?  Would adding an
entry help?  I'm kind of lost /proc/devices.  It's now mostly
non-functional legacy stuff we've been carrying around.  Is it
deprecated or do we intend to keep it around forever?

Ooh.. which also reminds me that I forgot to reserve the major number w/
lanana.  Will do that.

Thanks.

-- 
tejun

      reply	other threads:[~2008-09-02 12:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02 10:36 Problem w/ CONFIG_DEBUG_BLOCK_EXT_DEVT Alan D. Brunelle
2008-09-02 10:47 ` Tejun Heo
2008-09-02 10:55   ` Alan D. Brunelle
2008-09-02 10:57     ` Jens Axboe
2008-09-02 11:06     ` Tejun Heo
2008-09-02 12:20       ` [dm-devel] " Alasdair G Kergon
2008-09-02 12:23         ` Tejun Heo [this message]

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=48BD3031.3090905@kernel.org \
    --to=tj@kernel.org \
    --cc=Alan.Brunelle@hp.com \
    --cc=dm-devel@redhat.com \
    --cc=jens.axboe@oracle.com \
    --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;
as well as URLs for NNTP newsgroup(s).