From: Greg KH <greg@kroah.com>
To: Stanley Wang <stanley.wang@linux.co.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
PCI_Hot_Plug_Discuss <pcihpd-discuss@lists.sourceforge.net>
Subject: Re: [RFC] Get rid of all procfs stuff for PCI subsystem.
Date: Tue, 28 Jan 2003 13:56:44 -0800 [thread overview]
Message-ID: <20030128215644.GA7382@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301281747230.3171-100000@manticore.sh.intel.com>
On Tue, Jan 28, 2003 at 05:59:28PM +0800, Stanley Wang wrote:
> Hi, Greg
> When did I try to remove all procfs stuff from pci_hotplug_core.c,
> I found I could only cut little codes off.
But you cut out everything that was there, right? There wasn't much.
> So I suggest:
> How about to get rid of all procfs stuff for PCI subsystem?
> It could reduce about 700 lines codes from the kernel.
> I think we could get all information from sysfs, right?
> But it may break some user mode utilities.
If you look, a lot of it is now under a config option to just not enable
it at all, which helps out a lot.
thanks,
greg k-h
next prev parent reply other threads:[~2003-01-28 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 9:59 [RFC] Get rid of all procfs stuff for PCI subsystem Stanley Wang
2003-01-28 21:56 ` Greg KH [this message]
2003-01-28 22:21 ` [Pcihpd-discuss] " Scott Murray
2003-01-28 22:30 ` Greg KH
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=20030128215644.GA7382@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=stanley.wang@linux.co.intel.com \
/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