public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Shem Multinymous <multinymous@gmail.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Matt Domsch <Matt_Domsch@dell.com>,
	"Brown, Len" <len.brown@intel.com>,
	Henrique de Moraes Holschuh <hmh@debian.org>
Subject: Re: [PATCH] DMI: Decode and save OEM String information
Date: Wed, 2 Aug 2006 10:39:28 +0000	[thread overview]
Message-ID: <20060802103927.GI7601@ucw.cz> (raw)
In-Reply-To: <41840b750607270647w5a05ad00r613dbaf42bf04771@mail.gmail.com>

Hi!

> This teachs dmi_decode() how to to save OEM Strings 
> (type 11) information.
> OEM Strings are  the only safe way to identify some 
> hardware, e.g., the ThinkPad
> embedded controller used by the soon-to-be-submitted 
> tp_smapi driver.
> 
> Follows the "System Management BIOS (SMBIOS) 
> Specification"
> (http://www.dmtf.org/standards/smbios), and also the 
> userspace
> dmidecode.c code.

Looks good to me.

							Pavel
-- 
Thanks for all the (sleeping) penguins.

      parent reply	other threads:[~2006-08-02 10:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 13:47 [PATCH] DMI: Decode and save OEM String information Shem Multinymous
2006-07-27 16:10 ` Bjorn Helgaas
2006-07-27 16:42   ` Shem Multinymous
2006-07-28  3:27     ` Bjorn Helgaas
2006-07-28 12:49       ` Henrique de Moraes Holschuh
2006-07-28 18:37         ` Bjorn Helgaas
2006-07-28 20:52           ` Shem Multinymous
2006-07-28 21:08             ` Bjorn Helgaas
2006-07-28 22:07               ` Shem Multinymous
2006-07-29 12:55 ` Shem Multinymous
2006-07-29 16:29   ` Carl-Daniel U. Hailfinger
2006-07-29 17:09     ` Shem Multinymous
2006-08-02 12:19     ` Pavel Machek
2006-08-02 10:39 ` Pavel Machek [this message]

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=20060802103927.GI7601@ucw.cz \
    --to=pavel@suse.cz \
    --cc=Matt_Domsch@dell.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=hmh@debian.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=multinymous@gmail.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