From: Olof Johansson <olof@lixom.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jean Delvare <khali@linux-fr.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] dmi: export dmi data through debugfs
Date: Thu, 30 Sep 2010 09:31:39 -0500 [thread overview]
Message-ID: <20100930143139.GA25792@lixom.net> (raw)
In-Reply-To: <20100929222804.7f506ba5@lxorguk.ukuu.org.uk>
On Wed, Sep 29, 2010 at 10:28:04PM +0100, Alan Cox wrote:
> > Now if you really insist on exposing the whole DMI table through sysfs,
> > I can't prevent you from doing that. After all, ACPI already exposes
> > its tables under /sys/firmware/acpi/tables (mode 0400). But then you'd
> > rather expose the DMI entry point and tables
> > under /sys/firmware/dmi/tables for consistency, rather than using
> > debugfs. But again, I don't think it is adding any value over what we
> > already have.
>
> If you really the DMI data generally available run dmidecode in the boot
> scripts directed to a file. It even has a dump mode for this.
Sure. I didn't think a trivial patch like this would get pushback,
but that's a workable fallback for my use case.
Thanks,
-Olof
next prev parent reply other threads:[~2010-09-30 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 21:12 [PATCH] dmi: export dmi data through debugfs Olof Johansson
2010-09-29 7:34 ` Jean Delvare
2010-09-29 14:53 ` Olof Johansson
2010-09-29 15:11 ` Jean Delvare
2010-09-29 21:28 ` Alan Cox
2010-09-30 6:36 ` Jean Delvare
2010-09-30 14:31 ` Olof Johansson [this message]
2010-09-30 17:34 ` Andi Kleen
2010-09-30 17:59 ` Jean Delvare
2010-09-30 15:32 ` Bjorn Helgaas
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=20100930143139.GA25792@lixom.net \
--to=olof@lixom.net \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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