mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Mike Bell <kernel@mikebell.org>
Cc: greg@kroah.com, gregkh@suse.de, torvalds@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] Remove devfs from 2.6.12-git
Date: Wed, 22 Jun 2005 18:18:25 -0700	[thread overview]
Message-ID: <20050622181825.204fbcb7.akpm@osdl.org> (raw)
In-Reply-To: <20050623010031.GB17453@mikebell.org>

Mike Bell <kernel@mikebell.org> wrote:
>
> On Tue, Jun 21, 2005 at 08:10:19AM -0700, Greg KH wrote:
> > There might be some complaints.  But I doubt they would be from anyone
> > running a -mm tree as those people kind of know the current status of
> > things in the kernel.  There have been numerous warnings as to the fact
> > that this was going away, and I waited a _year_ to do this.
> 
> I use -mm and I'm complaining.

Thanks!

> It breaks a lot of my embedded setups which have read-only storage only
> and thus need /dev on devfs or tmpfs.

Well that's quite a problem.  We're certainly causing people such as
yourself to take on quite a lot of work.  But on the other hand we do want
the kernel to progress sanely, and that sometimes involves taking things
out.

I don't have enough info to know whether the world would be a better place
if we keep devfs, remove devfs or remove devfs even later on.  I don't
think anyone knows, which is why we're taking this little
disable-it-and-see-who-shouts approach.

  reply	other threads:[~2005-06-23  1:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21  6:29 Greg KH
2005-06-21  6:30 ` [PATCH] devfs: Remove devfs from the partition code Greg KH
2005-06-21  6:54 ` [GIT PATCH] Remove devfs from 2.6.12-git Andrew Morton
2005-06-21 13:50   ` Adrian Bunk
2005-06-21 15:10   ` Greg KH
2005-06-21 20:11     ` Andrew Morton
2005-06-21 20:52       ` Arjan van de Ven
2005-06-21 21:03         ` Andrew Morton
2005-06-21 21:16           ` Greg KH
2005-06-21 21:58             ` J.A. Magallon
2005-06-23  1:00     ` Mike Bell
2005-06-23  1:18       ` Andrew Morton [this message]
2005-06-23  2:13         ` Bill Gatliff
2005-06-23  4:59       ` Greg KH
2005-06-23  6:14         ` Miles Bader
2005-06-23  6:26           ` Greg KH
2005-06-23  6:36             ` Miles Bader
2005-06-23  7:03               ` Greg KH
2005-06-23 19:54             ` Kay Sievers
2005-06-23  6:34           ` Mike Bell
2005-06-23  6:37             ` Andrew Morton
2005-06-23  6:47               ` Mike Bell
2005-06-23  6:51               ` Greg KH
2005-06-23  6:38             ` Miles Bader
2005-06-23  6:28         ` Mike Bell
2005-06-23  6:48           ` Greg KH
2005-06-23  8:29             ` Mike Bell
2005-06-23 12:58               ` Theodore Ts'o
2005-06-24  8:24               ` Greg KH
2005-06-23 15:13             ` Per Liden
2005-07-18 16:36         ` Richard Gooch
2005-07-18 20:12           ` Jan Engelhardt
2005-07-18 22:29             ` Daniel Phillips
2005-07-19  2:51             ` Jim Crilly
2005-06-21 17:35 ` Carsten Otte
2005-06-23  4:08 David Brownell
2005-06-23  6:21 ` Miles Bader
2005-06-23  8:10 ` Russell King
2005-06-23  5:08 David Brownell
2005-06-23  5:22 ` Bill Gatliff

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=20050622181825.204fbcb7.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=kernel@mikebell.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

Powered by JetHome