From: Greg KH <greg@kroah.com>
To: Dave Jones <davej@redhat.com>, Doug Thompson <norsk5@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] EDAC and the sysfs
Date: Tue, 15 Nov 2005 09:24:05 -0800 [thread overview]
Message-ID: <20051115172405.GA13658@kroah.com> (raw)
In-Reply-To: <20051115003026.GA12266@redhat.com>
On Mon, Nov 14, 2005 at 07:30:26PM -0500, Dave Jones wrote:
> On Mon, Nov 14, 2005 at 02:31:05PM -0800, Greg Kroah-Hartman wrote:
> > On Mon, Nov 14, 2005 at 02:14:19PM -0800, Doug Thompson wrote:
> > >
> > > I am trying to design the sysfs interface tree for the
> > > new set of EDAC modules that are waiting for this
> > > interface, before being put into the kernel.
> > >
> > > Currently the original EDAC (bluesmoke) has its own
> > > /proc directory (/proc/mc) with files and a directory
> > > (0,1,2,...)for each memory controller on the system.
> > > This will be removed and the new information interface
> > > will be placed in the sysfs.
> > >
> > > One proposal is to place the information in
> > > /sys/devices/system in the following directories:
> >
> > Why not use /sys/firmware/ instead?
>
> Probably the same reason we don't have the cpufreq (for eg)
> stuff under /sys/firmware. Because it's poking hardware,
> not manipulating firmware.
>
> /sys/devices/system makes a lot more sense, as thats
> where the cpu level machine check stuff is (amongst other
> similar things).
Ok, that does make sense, thanks for explaining it.
greg k-h
next prev parent reply other threads:[~2005-11-15 17:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 22:14 [RFC] EDAC and the sysfs Doug Thompson
2005-11-14 22:31 ` Greg KH
2005-11-15 0:30 ` Dave Jones
2005-11-15 17:24 ` Greg KH [this message]
2005-11-15 0:47 ` Doug Thompson
2005-11-15 1:12 ` Doug Thompson
2005-11-15 17:25 ` Greg KH
2005-11-16 0:26 ` Doug Thompson
2005-11-17 7:05 ` Greg KH
2005-11-17 17:20 ` Doug Thompson
2005-11-17 17:18 ` Greg KH
2005-11-17 18:32 ` Kay Sievers
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=20051115172405.GA13658@kroah.com \
--to=greg@kroah.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=norsk5@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.