From: Matthew Wilcox <matthew@wil.cx>
To: Tejun Heo <tj@kernel.org>
Cc: jeff@garzik.org, linux-ide@vger.kernel.org,
James.Bottomley@HansenPartnership.com, bharrosh@panasas.com,
greg.freemyer@gmail.com, linux-scsi@vger.kernel.org,
brking@linux.vnet.ibm.com, liml@rtr.ca, jens.axboe@oracle.com,
viro@ftp.linux.org.uk, linux-kernel@vger.kernel.org,
device@lanana.org
Subject: Re: [PATCHSET 2.6.26-rc8] block: implement extended devt
Date: Thu, 3 Jul 2008 07:28:21 -0600 [thread overview]
Message-ID: <20080703132821.GE14894@parisc-linux.org> (raw)
In-Reply-To: <1215073986-4709-1-git-send-email-tj@kernel.org>
On Thu, Jul 03, 2008 at 05:33:00PM +0900, Tejun Heo wrote:
> I chose major 259 at my own whim. Is it okay to use this value? As
No. You need to get it assigned by LANANA (Torben Mathiasen
<device@lanana.org>). See Documentation/devices.txt.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-07-03 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 8:33 [PATCHSET 2.6.26-rc8] block: implement extended devt Tejun Heo
2008-07-03 8:33 ` [PATCH 1/6] block: misc updates Tejun Heo
2008-07-03 8:33 ` [PATCH 2/6] block: don't depend on consecutive minor space Tejun Heo
2008-07-03 8:33 ` [PATCH 3/6] block: implement extended minors Tejun Heo
2008-07-03 8:33 ` [PATCH 4/6] block: adjust formatting for large minors and add ext_range sysfs attr Tejun Heo
2008-07-03 8:33 ` [PATCH 5/6] sd/ide-disk: apply extended minors to sd and ide Tejun Heo
2008-07-03 8:33 ` [PATCH 6/6] block: implement CONFIG_DEBUG_BLOCK_EXT_DEVT Tejun Heo
2008-07-03 13:28 ` Matthew Wilcox [this message]
2008-07-03 15:54 ` [PATCHSET 2.6.26-rc8] block: implement extended devt Tejun Heo
2008-07-06 14:37 ` Tejun Heo
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=20080703132821.GE14894@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bharrosh@panasas.com \
--cc=brking@linux.vnet.ibm.com \
--cc=device@lanana.org \
--cc=greg.freemyer@gmail.com \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@kernel.org \
--cc=viro@ftp.linux.org.uk \
/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).