All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Ivan Khoronzhuk <ivan.khoronzhuk@globallogic.com>,
	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: Fri, 17 Apr 2015 16:12:49 +0200	[thread overview]
Message-ID: <1429279969.4600.0.camel@chaos.site> (raw)
In-Reply-To: <20150417134036.GA3671@codeblueprint.co.uk>

Hi Matt,

Le Friday 17 April 2015 à 14:40 +0100, Matt Fleming a écrit :
> 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.

Correct.

> 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?

Deal! :-)

-- 
Jean Delvare
SUSE L3 Support


WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <jdelvare@suse.de>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: dmidecode-devel@nongnu.org, matt.fleming@intel.com,
	ard.biesheuvel@linaro.org, linux-api@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	leif.lindholm@linaro.org, mikew@google.com, roy.franz@linaro.org,
	Ivan Khoronzhuk <ivan.khoronzhuk@globallogic.com>,
	msalter@redhat.com, grant.likely@linaro.org
Subject: Re: [dmidecode] [Patch 1/3] firmware: dmi_scan: rename dmi_table to dmi_decode_table
Date: Fri, 17 Apr 2015 16:12:49 +0200	[thread overview]
Message-ID: <1429279969.4600.0.camel@chaos.site> (raw)
In-Reply-To: <20150417134036.GA3671@codeblueprint.co.uk>

Hi Matt,

Le Friday 17 April 2015 à 14:40 +0100, Matt Fleming a écrit :
> 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.

Correct.

> 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?

Deal! :-)

-- 
Jean Delvare
SUSE L3 Support


_______________________________________________
https://lists.nongnu.org/mailman/listinfo/dmidecode-devel

  reply	other threads:[~2015-04-17 14:12 UTC|newest]

Thread overview: 41+ 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 ` Ivan Khoronzhuk
2015-04-02 12:57 ` [Patch 1/3] firmware: dmi_scan: rename dmi_table to dmi_decode_table Ivan Khoronzhuk
2015-04-02 12:57   ` Ivan Khoronzhuk
2015-04-15 11:51   ` Jean Delvare
2015-04-15 14:35   ` Matt Fleming
2015-04-15 14:35     ` Matt Fleming
2015-04-16  8:35     ` Jean Delvare
2015-04-16  8:35       ` Jean Delvare
2015-04-16 20:16       ` Ivan.khoronzhuk
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 12:50                 ` Jean Delvare
2015-04-17 13:40       ` Matt Fleming
2015-04-17 14:12         ` Jean Delvare [this message]
2015-04-17 14:12           ` [dmidecode] " Jean Delvare
2015-04-02 12:57 ` [Patch 2/3] firmware: dmi_scan: add SBMIOS entry and DMI tables Ivan Khoronzhuk
2015-04-02 12:57   ` Ivan Khoronzhuk
2015-04-03  9:36   ` Ivan.khoronzhuk
2015-04-15  4:19     ` Roy Franz
2015-04-15  4:19       ` Roy Franz
2015-04-16  0:54       ` Roy Franz
2015-04-16  0:54         ` Roy Franz
2015-04-16  6:48         ` Jean Delvare
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 12:56       ` Ivan.khoronzhuk
2015-04-16 15:44       ` Jean Delvare
2015-04-16 15:44         ` [dmidecode] " Jean Delvare
2015-04-16 17:27         ` subscivan
2015-04-16 17:32           ` Ivan.khoronzhuk
2015-04-16 17:32             ` Ivan.khoronzhuk
2015-04-17 13:02           ` Jean Delvare
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-02 12:57   ` 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=1429279969.4600.0.camel@chaos.site \
    --to=jdelvare@suse.de \
    --cc=ard.biesheuvel@linaro.org \
    --cc=dmidecode-devel@nongnu.org \
    --cc=grant.likely@linaro.org \
    --cc=ivan.khoronzhuk@globallogic.com \
    --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 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.