mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Douglas McNaught <doug@mcnaught.org>
To: Michael Thonke <iogl64nx@gmail.com>
Cc: Greg KH <gregkh@suse.de>, 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 08:32:28 -0400	[thread overview]
Message-ID: <m2oe71cdcz.fsf@Douglas-McNaughts-Powerbook.local> (raw)
In-Reply-To: <4322A160.1060809@gmail.com> (Michael Thonke's message of "Sat, 10 Sep 2005 11:03:28 +0200")

Michael Thonke <iogl64nx@gmail.com> writes:

>>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)?

If you don't know that stuff, or aren't willing to learn and report
bugs, don't run a kernel.org kernel--stick with your distro.

> Devfs is in for many years, why removing it in just some weeks?

It's been slated for removal for quite a while, and it was completely
disabled in the last kernel release.

-Doug

  reply	other threads:[~2005-09-10 12:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 21:45 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 [this message]
2005-09-10 21:55   ` Greg KH
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
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=m2oe71cdcz.fsf@Douglas-McNaughts-Powerbook.local \
    --to=doug@mcnaught.org \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --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

all inboxes | Powered by JetHome®