From: "Ivan.khoronzhuk" <ivan.khoronzhuk@globallogic.com>
To: Jean Delvare <jdelvare@suse.de>, Matt Fleming <matt@codeblueprint.co.uk>
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,
roy.franz@linaro.org
Subject: Re: [Patch 1/3] firmware: dmi_scan: rename dmi_table to dmi_decode_table
Date: Thu, 16 Apr 2015 23:16:59 +0300 [thread overview]
Message-ID: <553018BB.1080903@globallogic.com> (raw)
In-Reply-To: <20150416103511.55927ccc@endymion.delvare>
Hi Jean,
On 16.04.15 11:35, Jean Delvare wrote:
> Hi Matt,
>
> On Wed, 15 Apr 2015 15:35:30 +0100, Matt Fleming wrote:
>> On Thu, 02 Apr, at 03:57:01PM, Ivan Khoronzhuk wrote:
>>> The "dmi_table" function looks like data instance, but it does DMI
>>> table decode. This patch renames it to "dmi_decode_table" name as
>>> more appropriate. That allows us to use "dmi_table" name for correct
>>> purposes.
>>>
>>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@globallogic.com>
>>> ---
>>> drivers/firmware/dmi_scan.c | 10 +++++-----
>>> 1 file changed, 5 insertions(+), 5 deletions(-)
>> Looks good to me.
>>
>> Jean, do you want me to pick this patch up or are you going to?
> Good question, we need to agree on a strategy.
>
> There are 3 patch sets to consider here.
>
> 1* My patch fixing the UUID ordering bug. It must go in first and
> immediately, as it fixes a regression and will have to be backported
> to stable branches.
||
V
>
> 2* 2 older patches from Ivan which are currently in your efi-next tree
> if I'm not mistaken. Both were based on an old tree so they do not
> apply cleanly on kernel v4.0, I had to fix them up manually. I have
They are in master tree already.
> no idea if git would be able to merge them properly, as the fix
> above changed the context even more.
Current efi-next already merged, so you should base your patches on
top of last changes.
>
> 3* The 3 new patches from Ivan which I am reviewing now, which are not
> applied in any public tree AFAIK.
It shouldn't happen,
I've been verifying just now once again.
They are applied on top of linux_next cleanly.
Equal as on efi/next.
>
> 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.
>
> Thanks,
Jean,
I'm going to base my series
"firmware: dmi_scan: add SBMIOS entry point and DMI tables"
on top of linux next unless you have already your tree to pick up changes.
Please let me know, if you have one.
--
Regards,
Ivan Khoronzhuk
next prev parent reply other threads:[~2015-04-16 20:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 12:57 [Patch 0/3] firmware: dmi_scan: add SBMIOS entry point and DMI tables Ivan Khoronzhuk
2015-04-02 12:57 ` [Patch 1/3] firmware: dmi_scan: rename dmi_table to dmi_decode_table Ivan Khoronzhuk
2015-04-15 11:51 ` Jean Delvare
2015-04-15 14:35 ` Matt Fleming
2015-04-16 8:35 ` Jean Delvare
2015-04-16 20:16 ` Ivan.khoronzhuk [this message]
2015-04-17 8:54 ` Jean Delvare
2015-04-17 10:11 ` Ivan.khoronzhuk
2015-04-17 12:04 ` Ivan.khoronzhuk
2015-04-17 12:50 ` Jean Delvare
2015-04-17 13:40 ` Matt Fleming
2015-04-17 14:12 ` Jean Delvare
2015-04-02 12:57 ` [Patch 2/3] firmware: dmi_scan: add SBMIOS entry and DMI tables Ivan Khoronzhuk
2015-04-03 9:36 ` Ivan.khoronzhuk
2015-04-15 4:19 ` Roy Franz
2015-04-16 0:54 ` Roy Franz
2015-04-16 6:48 ` Jean Delvare
2015-04-16 17:08 ` Roy Franz
2015-04-16 9:52 ` Jean Delvare
2015-04-16 12:56 ` Ivan.khoronzhuk
2015-04-16 15:44 ` Jean Delvare
2015-04-16 17:27 ` subscivan
2015-04-16 17:32 ` Ivan.khoronzhuk
2015-04-17 13:02 ` Jean Delvare
2015-04-02 12:57 ` [Patch 3/3] Documentation: ABI: sysfs-firmware-dmi: add -entries suffix to file name Ivan Khoronzhuk
2015-04-15 11:52 ` Jean Delvare
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=553018BB.1080903@globallogic.com \
--to=ivan.khoronzhuk@globallogic.com \
--cc=ard.biesheuvel@linaro.org \
--cc=dmidecode-devel@nongnu.org \
--cc=grant.likely@linaro.org \
--cc=jdelvare@suse.de \
--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=matt@codeblueprint.co.uk \
--cc=mikew@google.com \
--cc=msalter@redhat.com \
--cc=roy.franz@linaro.org \
/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