From: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
To: Grant Likely <grant.likely@linaro.org>,
linux-kernel@vger.kernel.org, ard.biesheuvel@linaro.org
Cc: dmidecode-devel@nongnu.org, leif.lindholm@linaro.org,
matt.fleming@intel.com
Subject: Re: [Patch v2 0/2] firmware: dmi-sysfs: add SMBIOS entry point area raw attribute
Date: Tue, 27 Jan 2015 20:13:03 +0200 [thread overview]
Message-ID: <54C7D52F.1090207@linaro.org> (raw)
In-Reply-To: <20150127162331.70F43C41077@trevor.secretlab.ca>
On 01/27/2015 06:23 PM, Grant Likely wrote:
> On Mon, 26 Jan 2015 15:28:36 +0200
> , Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
> wrote:
>> Some utils, like dmidecode and smbios, needs to access SMBIOS entry
>> table area in order to get information like SMBIOS version, size, etc.
>> Currently it's done via /dev/mem. But for situation when /dev/mem
>> usage is disabled, the utils have to use dmi sysfs instead, which
>> doesn't represent SMBIOS entry. So this patch series adds SMBIOS
>> area to dmi sysfs in order to allow utils in question to work
>> correctly with dmi sysfs.
>>
>> v1: https://lkml.org/lkml/2015/1/23/643
> Hi Ivan,
>
> The change looks good to me, but it is an ABI addition, so it needs to
> be documented. You'll need to add a description to:
>
> Documentation/ABI/testing/sysfs-testing/sysfs-firmware-dmi
Ups...
Ok, It'll be in Documentation/ABI/testing/sysfs-firmware-dmi
Thanks!
>
> Second, (minor point), there is no reason to split this up into two
> patches. It is one feature, and would be better as a single patch.
>
> g.
Ok, it'll be one patch, including documentation
>
>> v2..v1:
>> firmware: dmi_scan: add symbol to get SMBIOS entry area
>> - used additional static var to hold SMBIOS raw table size
>> - changed format of get_smbios_entry_area symbol
>> returned pointer on const smbios table
>>
>> firmware: dmi-sysfs: add SMBIOS entry point area attribute
>> - adopted to updated get_smbios_entry_area symbol
>> - removed redundant array to save smbios table
>>
>> Ivan Khoronzhuk (2):
>> firmware: dmi_scan: add symbol to get SMBIOS entry area
>> firmware: dmi-sysfs: add SMBIOS entry point area attribute
>>
>> drivers/firmware/dmi-sysfs.c | 42 ++++++++++++++++++++++++++++++++++++++++++
>> drivers/firmware/dmi_scan.c | 26 ++++++++++++++++++++++++++
>> include/linux/dmi.h | 3 +++
>> 3 files changed, 71 insertions(+)
>>
>> --
>> 1.9.1
>>
prev parent reply other threads:[~2015-01-27 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 13:28 [Patch v2 0/2] firmware: dmi-sysfs: add SMBIOS entry point area raw attribute Ivan Khoronzhuk
2015-01-26 13:28 ` [Patch v2 1/2] firmware: dmi_scan: add symbol to get SMBIOS entry area Ivan Khoronzhuk
2015-01-26 13:32 ` Ard Biesheuvel
2015-01-26 13:28 ` [Patch v2 2/2] firmware: dmi-sysfs: add SMBIOS entry point area attribute Ivan Khoronzhuk
2015-01-26 13:34 ` Ard Biesheuvel
2015-01-27 11:35 ` [Patch v2 0/2] firmware: dmi-sysfs: add SMBIOS entry point area raw attribute Matt Fleming
2015-01-27 16:23 ` Grant Likely
2015-01-27 18:13 ` Ivan Khoronzhuk [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=54C7D52F.1090207@linaro.org \
--to=ivan.khoronzhuk@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=dmidecode-devel@nongnu.org \
--cc=grant.likely@linaro.org \
--cc=leif.lindholm@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.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