From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Dave Jones <davej@redhat.com>,
dsaxena@plexity.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Transition /proc/cpuinfo -> sysfs
Date: Sat, 14 Aug 2004 23:33:19 -0700 [thread overview]
Message-ID: <20040815063318.GA1787@kroah.com> (raw)
In-Reply-To: <20040814231153.24a4f8e7.akpm@osdl.org>
On Sat, Aug 14, 2004 at 11:11:53PM -0700, Andrew Morton wrote:
> Dave Jones <davej@redhat.com> wrote:
> >
> > > My understanding is that goal is to
> > > make /proc slowly return to it's original purpose (process-information)
> > > and move other data out into sysfs.
> >
> > I don't think thats a realistic goal.
>
> It may be realistic if we try hard enough, but I don't think it's a
> desirable one at this time. I'd prefer that I, Deepak and everyone else be
> spending cycles on higher-priority things than these patches. Sorry.
But things like this are fun to do at times :)
Anyway, that being said, I'm going to keep Deepak's patches around in my
personal trees and see how well they work out as they are something that
I've personally been interested in doing for quite some time. If, after
a while, things look better, I'll ask for a trial time in the -mm tree
for them.
thanks,
greg k-h
next prev parent reply other threads:[~2004-08-15 6:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 22:41 [PATCH 0/3] Transition /proc/cpuinfo -> sysfs Deepak Saxena
2004-08-11 22:42 ` [PATCH 1/3] [Generic] " Deepak Saxena
2004-08-11 22:44 ` [PATCH 2/3] [i386] " Deepak Saxena
2004-08-11 22:47 ` [PATCH 3/3] [ARM] " Deepak Saxena
2004-08-11 22:47 ` [PATCH 0/3] " Deepak Saxena
2004-08-11 23:13 ` Dave Jones
2004-08-11 23:42 ` Deepak Saxena
2004-08-11 23:59 ` Dave Jones
2004-08-12 2:45 ` Deepak Saxena
2004-08-12 11:07 ` Dave Jones
2004-08-15 6:11 ` Andrew Morton
2004-08-15 6:33 ` Greg KH [this message]
2004-08-12 5:03 ` Lamont R. Peterson
2004-08-12 10:56 ` Dave Jones
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=20040815063318.GA1787@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=dsaxena@plexity.net \
--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