From: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: linux-kernel@vger.kernel.org, ard.biesheuvel@linaro.org,
leif.lindholm@linaro.org
Subject: Re: [Patch v2] firmware: dmi_scan: fix dmi scan to handle "End of Table" structure
Date: Wed, 18 Feb 2015 15:20:05 +0200 [thread overview]
Message-ID: <54E49185.6080000@linaro.org> (raw)
In-Reply-To: <20150218130436.GB5648@codeblueprint.co.uk>
Ok, I'll correct commit msg like:
But after adding initial SMBIOS v3 support (fc43026278b23b3515cf8f909ec29df94b3ae1a2)
the 127-0 entry is nothandled any more, as result it's not created in sysfs.
On 02/18/2015 03:04 PM, Matt Fleming wrote:
> On Wed, 04 Feb, at 04:22:05PM, Ivan Khoronzhuk wrote:
>> The dmi-sysfs should create "End of Table" entry, that is type 127.
>> But after adding initial SMBIOS v3 support the 127-0 entry is not
>> handled any more, as result it's not created in sysfs.
>> This is important because the size of whole DMI table must correspond
>> to sum of all DMI entry sizes.
>>
>> So move "end-of-table" check after it's handled by decode.
>>
>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
>> ---
>>
>> v2..v1:
>> Move end of table check after it's handled instead of removing
>> Correct commit
>>
>> drivers/firmware/dmi_scan.c | 13 +++++++------
>> 1 file changed, 7 insertions(+), 6 deletions(-)
> The way that the commit log is written makes this sound like a
> regression. If that's the case, then you need to list which commit
> introduced the regression, because that will tell me whether it needs
> tagging for stable.
>
next prev parent reply other threads:[~2015-02-18 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 14:22 [Patch v2] firmware: dmi_scan: fix dmi scan to handle "End of Table" structure Ivan Khoronzhuk
2015-02-05 10:36 ` Ard Biesheuvel
2015-02-18 10:18 ` Ivan Khoronzhuk
2015-02-18 13:04 ` Matt Fleming
2015-02-18 13:20 ` Ivan Khoronzhuk [this message]
2015-02-18 13:38 ` Matt Fleming
2015-02-18 13:54 ` 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=54E49185.6080000@linaro.org \
--to=ivan.khoronzhuk@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=leif.lindholm@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
/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.