public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>, Jan Blunck <jblunck@suse.de>,
	linux-arch@vger.kernel.org, viro@zeniv.linux.org.uk,
	torvalds@osdl.org, akpm@osdl.org, adam@yggdrasil.com
Subject: Re: [PATCH] driver-core: devtmpfs - driver core maintained /dev	tmpfs
Date: Sat, 02 May 2009 12:59:33 -0400	[thread overview]
Message-ID: <49FC7BF5.8080502@garzik.org> (raw)
In-Reply-To: <20090502071636.GA9487@infradead.org>

Christoph Hellwig wrote:
> On Thu, Apr 30, 2009 at 03:23:42PM +0200, Kay Sievers wrote:
>> From: Kay Sievers <kay.sievers@vrfy.org>
>> Subject: driver-core: devtmpfs - driver core maintained /dev tmpfs
> 
> Umm, guys this needs much broader discussion than just sneaking in
> a patch under the covers.
> 
> It basically does re-introduce devfs under a different name, and from
> looking at the implementation it might not be quite as bad a Gooch's
> original, but it's certainly worse than Adam Richters rewrite the we
> never ended up merging.

I was interested in this Richter devfs rewrite, since I was unfamiliar 
with it.

For the benefit of the thread, here is a URL that people can examine:

	http://marc.info/?l=linux-kernel&m=104138806530375&w=2

Regards,

	Jeff

  parent reply	other threads:[~2009-05-02 16:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1241097822.2516.3.camel@poy>
2009-05-02  7:16 ` [PATCH] driver-core: devtmpfs - driver core maintained /dev tmpfs Christoph Hellwig
2009-05-02 11:34   ` Kay Sievers
2009-05-02 20:22     ` Alan Jenkins
2009-05-02 21:39       ` Kay Sievers
2009-05-02 22:04         ` Alan Jenkins
2009-05-03  7:29           ` Michael Tokarev
2009-05-02 21:41       ` Alan Jenkins
2009-05-02 21:54         ` Greg KH
2009-05-02 21:59         ` Kay Sievers
2009-05-02 16:59   ` Jeff Garzik [this message]
2009-05-02 17:57     ` Kay Sievers

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=49FC7BF5.8080502@garzik.org \
    --to=jeff@garzik.org \
    --cc=adam@yggdrasil.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=jblunck@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=viro@zeniv.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