public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ed L Cashin <ecashin@coraid.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, Greg K-H <greg@kroah.com>
Subject: Re: [PATCH 2.6.11] aoe [7/12]: support configuration of AOE_PARTITIONS from Kconfig
Date: Tue, 29 Mar 2005 17:57:05 +0100	[thread overview]
Message-ID: <20050329165705.GA31013@infradead.org> (raw)
In-Reply-To: <87wtrqtn2n.fsf@coraid.com>

On Tue, Mar 29, 2005 at 11:48:48AM -0500, Ed L Cashin wrote:
> I don't know if it matters now that we have udev.  When udev manages
> the device nodes it all just works,

But most peopel still don't use udev.

> If you're saying that it's bad in principal, then that's another
> story.  If that's what you mean, then it's a Linux policy issue, and
> to follow convention I'd think that we'd need another major number.
> That would be like the partitionable md devices, etc.

Yes, it's a policy issue.  We don't do this weird config option anywhere
else.


  reply	other threads:[~2005-03-29 16:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87mztbi79d.fsf@coraid.com>
2005-03-17 23:46 ` [PATCH 2.6.11] aoe [1/12]: remove too-low cap on minor number Greg KH
2005-03-18 20:13   ` Ed L Cashin
2005-03-18 20:14   ` [PATCH 2.6.11] aoe [4/12]: handle distros that have a udev rules file instead of dir Ed L. Cashin
2005-03-24 14:59   ` [PATCH 2.6.11] aoe [1/12]: remove too-low cap on minor number ecashin
2005-03-24 15:09   ` [PATCH 2.6.11] aoe [2/12]: allow multiple aoe devices with same MAC addr ecashin
2005-03-24 15:13   ` [PATCH 2.6.11] aoe [3/12]: update driver version to 6 ecashin
2005-03-24 15:15   ` [PATCH 2.6.11] aoe [4/12]: handle distros that have a udev rules file instead of dir ecashin
2005-03-24 15:17   ` [PATCH 2.6.11] aoe [5/12]: don't try to free null bufpool ecashin
2005-03-24 15:58     ` Arjan van de Ven
2005-03-24 17:04       ` ecashin
2005-03-24 17:17         ` Arjan van de Ven
2005-03-25 14:37           ` Jesper Juhl
2005-03-29 12:31           ` Jens Axboe
2005-03-24 15:19   ` [PATCH 2.6.11] aoe [6/12]: Alexey Dobriyan sparse cleanup ecashin
2005-03-24 15:21   ` [PATCH 2.6.11] aoe [7/12]: support configuration of AOE_PARTITIONS from Kconfig ecashin
2005-03-28 17:07     ` Christoph Hellwig
2005-03-29 16:06       ` Ed L Cashin
2005-03-29 16:25         ` Christoph Hellwig
2005-03-29 16:48           ` Ed L Cashin
2005-03-29 16:57             ` Christoph Hellwig [this message]
2005-04-07 18:28               ` Ed L Cashin
2005-04-07 18:49                 ` Greg KH
2005-04-07 18:56                   ` Ed L Cashin
2005-04-07 23:08                     ` Greg KH
2005-04-08 13:54                       ` Ed L Cashin
2005-03-24 15:23   ` [PATCH 2.6.11] aoe [8/12]: document env var for specifying number of partitions per dev ecashin
2005-03-24 15:25   ` [PATCH 2.6.11] aoe [9/12]: add note about the need for deadlock-free sk_buff allocation ecashin
2005-03-24 15:27   ` [PATCH 2.6.11] aoe [10/12]: Randy Dunlap: avoid warnings on sparc64 ecashin
2005-03-24 15:30   ` [PATCH 2.6.11] aoe [11/12]: add support for disk statistics ecashin
2005-03-24 15:32   ` [PATCH 2.6.11] aoe [12/12]: send outgoing packets in order ecashin

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=20050329165705.GA31013@infradead.org \
    --to=hch@infradead.org \
    --cc=ecashin@coraid.com \
    --cc=greg@kroah.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