[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150417134036.GA3671@codeblueprint.co.uk>
Date: Fri, 17 Apr 2015 14:40:36 +0100
From: Matt Fleming <matt@...eblueprint.co.uk>
To: Jean Delvare <jdelvare@...e.de>
Cc: Ivan Khoronzhuk <ivan.khoronzhuk@...ballogic.com>,
linux-kernel@...r.kernel.org, matt.fleming@...el.com,
ard.biesheuvel@...aro.org, grant.likely@...aro.org,
linux-api@...r.kernel.org, linux-doc@...r.kernel.org,
mikew@...gle.com, dmidecode-devel@...gnu.org,
leif.lindholm@...aro.org, msalter@...hat.com, roy.franz@...aro.org
Subject: Re: [Patch 1/3] firmware: dmi_scan: rename dmi_table to
dmi_decode_table
On Thu, 16 Apr, at 10:35:11AM, Jean Delvare wrote:
>
> I don't really care who picks these patches up and sends them to Linus,
> but I think they should all follow the same route so that Linus has as
> little merge work to do as possible. So either you pick them all, or I
> do. If I do, you'll have to drop the 2 patches you have in efi-next.
> Again I'm fine either way, so please let me know what makes your life
> easier and let's do that.
As was mentioned by Ivan, the following patches have already been merged
by Linus,
f617b0f32da2 ("firmware: dmi_scan: Use full dmi version for SMBIOS3")
e4b1dec448af ("firmware: dmi_scan: Use direct access to static vars")
so no patches need to be dropped from my tree and there are no pending
DMI/SMBIOS patches in any of my branches.
How about you go ahead and collect all the patches and send them to
Linus? I'm happy to pickup any patches in the future if I'm explicitly
asked, but only if OK'd by you, Jean.
Sound OK to everyone?
--
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists