mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Don Zickus <dzickus@redhat.com>,
	mikew@google.com, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: /sys/firmware/dmi name change?
Date: Tue, 5 Apr 2011 10:30:28 -0700	[thread overview]
Message-ID: <20110405173028.GC20622@kroah.com> (raw)
In-Reply-To: <4D9B4E3A.4090601@redhat.com>

On Tue, Apr 05, 2011 at 01:15:38PM -0400, Prarit Bhargava wrote:
> commit 948af1f0bbc8526448e8cbe3f8d3bf211bdf5181 (and follow on commits)
> introduced a new firmware directory called /sys/firmware/dmi which
> provides broken out SMBIOS entries for userspace.
> 
> In a previous discussion I've mentioned that it would be a good idea for
> us to move away from using 'dmi' towards using 'smbios' and centralizing
> the SMBIOS code that is scattered throughout the kernel.  One of my
> changes was to export the SMBIOS information in a similar way that Mike
> did in drivers/firmware/dmi-sysfs.c.
> 
> Since this API is new for 2.6.39, can we change the name of the
> directory to /sys/firmware/smbios?  Otherwise in 2.6.40, when further
> changes are introduced to use SMBIOS in the kernel we will have to
> change something that has been stable for one release.
> 
> Mike?  Greg?  Alan?  What do you think?  IIUC, the interface isn't yet
> "stable" so it should be changed now, correct?

Fine with me if Mike's ok with it as well.  If so, someone send me a
patch quick!

thanks,

greg k-h

  parent reply	other threads:[~2011-04-05 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 17:15 Prarit Bhargava
2011-04-05 17:23 ` Alan Cox
2011-04-05 17:30 ` Greg KH [this message]
2011-04-05 18:57   ` Mike Waychison
2011-04-05 18:14 ` Prarit Bhargava

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=20110405173028.GC20622@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dzickus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikew@google.com \
    --cc=prarit@redhat.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

all inboxes | Powered by JetHome®