From: Greg KH <gregkh@suse.de>
To: Michael Thonke <iogl64nx@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] Remove devfs from 2.6.13
Date: Sat, 10 Sep 2005 14:55:40 -0700 [thread overview]
Message-ID: <20050910215540.GB15645@suse.de> (raw)
In-Reply-To: <4322A160.1060809@gmail.com>
On Sat, Sep 10, 2005 at 11:03:28AM +0200, Michael Thonke wrote:
> Hello Greg,
>
> just for understanding the problem right. Some questions.
> Greg KH schrieb:
>
> >Here are the same "delete devfs" patches that I submitted for 2.6.12.
> >It rips out all of devfs from the kernel and ends up saving a lot of
> >space. Since 2.6.13 came out, I have seen no complaints about the fact
> >that devfs was not able to be enabled anymore, and in fact, a lot of
> >different subsystems have already been deleting devfs support for a
> >while now, with apparently no complaints (due to the lack of users.)
> >
> >
> How could users really say/complain what brakage they have, in fact they
> don't even know the relationship between all that
> ( e.g drivers -> devfs -> sysfs or other programs that rely on devfs)?
Their machines would not boot. :)
> They aren't all developers to encrypt the "magic" bug reports/debug messages
> spreading over the screen.
What do you mean?
> >I mean, how can you go wrong with deleting over 8000 lines of kernel
> >code :)
> >
> >
> Right, it's a good/right work to remove dispensable code from kernel.
> Even it makes it easier to maintain the code but what happen if
> there is an "for now" an unresolved/unknown problem which no one notice
> so far?
>
> Devfs is in for many years, why removing it in just some weeks?
It's been told and widly known that it was going to be removed last
July. In July 2004 this happened, so people have known for over a year.
How much longer do you expect me to give people?
> I think this is a bad solution because on the one hand you "force" to
> remove devfs due it's crappy naming sheme and on the other hand
> offering to add such thing again which brakes ALSA and other.
> *confused* Even if it has only 300 lines of code.
>
> This is not consistent with the intention to remove devfs forever.
> Either say "live with it or die" or leave it as it is.
"die." :)
I never said that ndevfs was to be a solution for anyone, just for
people who really complained about Linux not having an in-kernel
devfs-like solution. And if they worry about this, then they can keep
that patch outside of the main kernel tree for their distros quite
easily.
thanks,
greg k-h
next prev parent reply other threads:[~2005-09-10 21:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 21:45 [GIT PATCH] Remove devfs from 2.6.13 Greg KH
2005-09-10 8:27 ` Mike Bell
2005-09-10 21:52 ` Greg KH
2005-09-10 23:03 ` Mike Bell
2005-09-11 5:09 ` Greg KH
2005-09-12 13:40 ` Steven Rostedt
2005-09-14 20:00 ` Mike Bell
2005-09-14 20:28 ` Kyle Moffett
2005-09-14 23:06 ` Greg KH
2005-09-15 2:10 ` Ioan Ionita
2005-09-10 9:03 ` [GIT PATCH] " Michael Thonke
2005-09-10 12:32 ` Douglas McNaught
2005-09-10 21:55 ` Greg KH [this message]
2005-09-10 14:15 ` J.A. Magallon
2005-09-10 23:24 ` J.A. Magallon
2005-09-10 23:30 ` Greg KH
2005-09-11 0:48 ` David Lang
2005-09-11 3:07 ` Greg KH
2005-09-11 6:08 ` David Lang
2005-09-11 7:05 ` Arjan van de Ven
2005-09-11 7:13 ` Valdis.Kletnieks
2005-09-11 7:20 ` David Lang
2005-09-11 11:02 ` Theodore Ts'o
2005-09-12 8:01 ` Martin Schlemmer
2005-09-11 17:15 ` Greg KH
2005-09-11 11:35 ` Bastian Blank
2005-09-11 11:42 ` CaT
2005-09-11 17:17 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-09-11 11:44 linux
2005-09-11 15:43 ` Kyle Moffett
2005-09-14 20:01 ` Mike Bell
2005-09-14 20:13 ` Kyle Moffett
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=20050910215540.GB15645@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=iogl64nx@gmail.com \
--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