From: tmhikaru@gmail.com
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kernel@vger.kernel.org, Zhenzhong Duan <zhenzhong.duan@oracle.com>
Subject: Re: [PATCH 2/2] dmi_scan: Refactor dmi_scan_machine(), {smbios,dmi}_present()
Date: Sun, 17 Feb 2013 01:55:58 -0500 [thread overview]
Message-ID: <20130217065558.GA2113@roll> (raw)
In-Reply-To: <1361037742.5374.441.camel@deadeye.wl.decadent.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On Sat, Feb 16, 2013 at 06:02:22PM +0000, Ben Hutchings wrote:
> Move the calls to memcpy_fromio() up into the loop in
> dmi_scan_machine(), and move the signature checks back down into
> dmi_decode(). We need to check at 16-byte intervals but keep a
> 32-byte buffer for an SMBIOS entry, so shift the buffer after each
> iteration.
>
> Merge smbios_present() into dmi_present(), so we look for an SMBIOS
> signature at the beginning of the given buffer and then for a DMI
> signature at an offset of 16 bytes.
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
> This file mixes up __iomem and regular pointers a lot, and this patch
> fixes some but not all of those instances. Presumably it is quite
> safe to read a BIOS image with any mov instructions the compiler
> generates, but in that case maybe we should explicitly cast away the
> __iomem qualifier in dmi_ioremap()?
>
> Tim, you might like to test that this doesn't cause a regression
> of the previous fix.
I can confirm that this works just as well as the last patch you gave me.
I'm sorry that it took me a while to reply.
Tim McGrath
[-- Attachment #2: Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2013-02-17 6:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 18:00 [PATCH 1/2] dmi_scan: Fix missing check for _DMI_ signature in smbios_present() Ben Hutchings
2013-02-16 18:02 ` [PATCH 2/2] dmi_scan: Refactor dmi_scan_machine(), {smbios,dmi}_present() Ben Hutchings
2013-02-17 6:03 ` tmhikaru
2013-02-17 6:55 ` tmhikaru [this message]
2013-03-04 20:09 ` tmhikaru
2013-03-05 5:23 ` Ben Hutchings
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=20130217065558.GA2113@roll \
--to=tmhikaru@gmail.com \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenzhong.duan@oracle.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