public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Russ Anderson <rja@sgi.com>
Cc: mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org,
	Jack Steiner <steiner@sgi.com>, Greg KH <greg@kroah.com>
Subject: Re: x86 BIOS interface for partitioning and system serial number on SGI UV
Date: Mon, 04 Aug 2008 17:59:42 -0700	[thread overview]
Message-ID: <4897A5FE.9070703@zytor.com> (raw)
In-Reply-To: <20080804221951.GA252105@sgi.com>

Russ Anderson wrote:
>> This really seems more that it should belong in sysfs -- 
>> /sys/class/firmware presumably.
> 
> /proc/sgi_uv already exists, similar to /proc/sgi_sn on Itanium systems.
> 
> Would it be /sys/class/firmware?  Reading Documentation/sysfs-rules.txt
> seems to indicate somewhere under /sys/devices, such as /sys/devices/system/,
> but I may be wrong.

/sys/class/firmware is usually where firmware-related things end up, but 
gregkh is the authority on sysfs organization.

	-hpa

  parent reply	other threads:[~2008-08-05  1:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 19:57 x86 BIOS interface for partitioning and system serial number on SGI UV Russ Anderson
2008-08-01 17:34 ` H. Peter Anvin
2008-08-04 22:19   ` Russ Anderson
2008-08-05  0:50     ` H. Peter Anvin
2008-08-05  0:59     ` H. Peter Anvin [this message]
2008-08-05  3:54       ` Greg KH
2008-08-05 16:32         ` Russ Anderson
2008-08-05 16:53           ` Greg KH
2008-08-05 19:22             ` Russ Anderson
2008-08-05 23:06         ` Russ Anderson
2008-08-05  5:21     ` Kyle Moffett
2008-08-05 14:35       ` Mike Travis
2008-08-05 15:40         ` H. Peter Anvin
2008-08-05 15:56           ` Mike Travis
  -- strict thread matches above, loose matches on Subject: below --
2008-08-05 17:24 H. Peter Anvin

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=4897A5FE.9070703@zytor.com \
    --to=hpa@zytor.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rja@sgi.com \
    --cc=steiner@sgi.com \
    --cc=tglx@linutronix.de \
    /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