From: Jean Delvare <jdelvare@suse.de>
To: "Ivan.khoronzhuk" <ivan.khoronzhuk@globallogic.com>
Cc: linux-kernel@vger.kernel.org, matt.fleming@intel.com,
ard.biesheuvel@linaro.org, grant.likely@linaro.org,
linux-api@vger.kernel.org, linux-doc@vger.kernel.org,
mikew@google.com, dmidecode-devel@nongnu.org,
leif.lindholm@linaro.org, msalter@redhat.com
Subject: Re: [Patch] firmware: dmi_scan: split dmisubsystem from dmi-sysfs
Date: Thu, 02 Apr 2015 17:08:22 +0200 [thread overview]
Message-ID: <1427987302.4281.309.camel@chaos.site> (raw)
In-Reply-To: <551D3DE4.8040409@globallogic.com>
Le Thursday 02 April 2015 à 16:02 +0300, Ivan.khoronzhuk a écrit :
> Hi Jean,
> Sorry for the late reply.
> I've send new series
> "[Patch 0/3] firmware: dmi_scan: add SBMIOS entry point and DMI tables"
> with all last propositions.
Thanks Ivan, no problem. I'll look at it when I have time.
Two related notes:
* On week from April 13th to 17th, this is Hack Week 12 at SUSE. This
time I decided to work on dmidecode. I plan to add full support for
SMBIOS 3.0.0, including the new entry point format. Then I'll work on
integrating your work (the sysfs interface.) Project page:
https://hackweek.suse.com/12/projects/766
If you or anyone else want to participate, you are very welcome. Ideally
we would release dmidecode 2.13 at the end of that week.
* Do you know of any hardware already implementing SMBIOS 3.0 (either
the new entry point format, or the new enumerated values, or both)?
Having a real-world example would make testing much easier.
Thanks,
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2015-04-02 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 20:57 [Patch] firmware: dmi_scan: split dmisubsystem from dmi-sysfs Ivan Khoronzhuk
2015-03-19 15:30 ` Jean Delvare
2015-03-19 17:35 ` Ivan.khoronzhuk
2015-03-20 8:16 ` Jean Delvare
[not found] ` <1426852834.2727.25.camel@intel.com>
2015-03-20 12:35 ` Jean Delvare
2015-04-02 13:02 ` Ivan.khoronzhuk
2015-04-02 15:08 ` Jean Delvare [this message]
2015-04-03 7:21 ` Ivan.khoronzhuk
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=1427987302.4281.309.camel@chaos.site \
--to=jdelvare@suse.de \
--cc=ard.biesheuvel@linaro.org \
--cc=dmidecode-devel@nongnu.org \
--cc=grant.likely@linaro.org \
--cc=ivan.khoronzhuk@globallogic.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mikew@google.com \
--cc=msalter@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;
as well as URLs for NNTP newsgroup(s).