All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mario_Limonciello@Dell.com
Cc: Allen_Hung@Dell.com, jdelvare@suse.com,
	rmk+kernel@arm.linux.org.uk, somlo@cmu.edu,
	bjorn.andersson@sonymobile.com, jens.wiklander@linaro.org,
	agross@codeaurora.org, arnd@arndb.de, sudeep.holla@arm.com,
	eric@anholt.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] dmi-id: add dmi/id/oem group for exporting oem strings to sysfs
Date: Wed, 31 Aug 2016 16:43:26 +0200	[thread overview]
Message-ID: <20160831144326.GA24945@kroah.com> (raw)
In-Reply-To: <488533a5959a46eca5f037cca26f42bd@ausx13mpc124.AMER.DELL.COM>

On Wed, Aug 31, 2016 at 02:01:23PM +0000, Mario_Limonciello@Dell.com wrote:
> Hi Greg,
> 
> > -----Original Message-----
> > From: Greg Kroah-Hartman [mailto:gregkh@linuxfoundation.org]
> > Sent: Wednesday, August 31, 2016 7:40 AM
> > To: Hung, Allen <Allen_Hung@Dell.com>
> > Cc: Jean Delvare <jdelvare@suse.com>; Russell King
> > <rmk+kernel@arm.linux.org.uk>; Gabriel Somlo <somlo@cmu.edu>; Bjorn
> > Andersson <bjorn.andersson@sonymobile.com>; Jens Wiklander
> > <jens.wiklander@linaro.org>; Andy Gross <agross@codeaurora.org>; Arnd
> > Bergmann <arnd@arndb.de>; Sudeep Holla <sudeep.holla@arm.com>; Eric
> > Anholt <eric@anholt.net>; linux-kernel@vger.kernel.org; Limonciello, Mario
> > <Mario_Limonciello@Dell.com>
> > Subject: Re: [PATCH v3 2/2] dmi-id: add dmi/id/oem group for exporting oem
> > strings to sysfs
> > 
> > On Mon, Aug 15, 2016 at 05:22:05PM +0800, Allen Hung wrote:
> > > The oem strings in DMI system identification information of the BIOS
> > > have been parsed and stored as dmi devices in dmi_scan.c but they are
> > > not exported to userspace via sysfs.
> > >
> > > The patch intends to export oem strings to sysfs device /sys/class/dmi/id.
> > > As the number of oem strings are dynamic, a group "oem" is added to
> > > the device and the strings will be added to the group as string1,
> > > string2, ..., and stringN.
> > >
> > > Signed-off-by: Allen Hung <allen_hung@dell.com>
> > > ---
> > >  drivers/firmware/Kconfig  |   9 ++++
> > >  drivers/firmware/dmi-id.c | 116
> > > ++++++++++++++++++++++++++++++++++++++++++++++
> > >  2 files changed, 125 insertions(+)
> > >
> > > diff --git a/drivers/firmware/Kconfig b/drivers/firmware/Kconfig index
> > > 6664f11..885a6c9 100644
> > > --- a/drivers/firmware/Kconfig
> > > +++ b/drivers/firmware/Kconfig
> > > @@ -119,6 +119,15 @@ config DMIID
> > >  	  information from userspace through /sys/class/dmi/id/ or if you want
> > >  	  DMI-based module auto-loading.
> > >
> > > +config DMIID_OEM_STRINGS
> > > +	bool "Export OEM strings in SMBIOS/DMI via sysfs to userspace"
> > > +	depends on DMIID
> > > +	default n
> > > +	help
> > > +	  Say Y here if you want to query OEM strings (as part of the information
> > > +	  contained in SMBIOS/DMI system identification) from userspace
> > through
> > > +	  /sys/class/dmi/id/oem/.
> > 
> > Why wouldn't you want these?
> > 
> 
> Jean Delvare would rather see this implemented in userspace dmidecode.
> Jean raised a concern in an earlier submission that this runs on every
> machine (https://lkml.org/lkml/2016/8/2/799).

Ah, yeah, just use dmidecode, much simpler, keeps the kernel smaller, I
like it.

thanks,

greg k-h

  reply	other threads:[~2016-08-31 14:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15  9:22 [PATCH v3 2/2] dmi-id: add dmi/id/oem group for exporting oem strings to sysfs Allen Hung
2016-08-31 12:40 ` Greg Kroah-Hartman
2016-08-31 14:01   ` Mario_Limonciello
2016-08-31 14:43     ` Greg KH [this message]
2016-08-31 15:47       ` Jean Delvare
2016-08-31 21:51         ` Mario_Limonciello
2016-09-01 18:01           ` Jean Delvare
2016-09-01 19:14             ` Mario_Limonciello
2017-05-01 11:39               ` Jean Delvare
2017-05-01 20:58                 ` Mario.Limonciello
2017-05-22  7:47                   ` Jean Delvare
2017-05-22 19:53                     ` Mario.Limonciello

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=20160831144326.GA24945@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Allen_Hung@Dell.com \
    --cc=Mario_Limonciello@Dell.com \
    --cc=agross@codeaurora.org \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=eric@anholt.net \
    --cc=jdelvare@suse.com \
    --cc=jens.wiklander@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=somlo@cmu.edu \
    --cc=sudeep.holla@arm.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.