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
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
On Fri, 17 Apr 2015 15:04:23 +0300, Ivan.khoronzhuk wrote:
> On 17.04.15 13:11, Ivan.khoronzhuk wrote:
> > On 17.04.15 11:54, Jean Delvare wrote:
> >> I have no formal tree yet, but my current patch set can be seen at:
> >> http://jdelvare.nerim.net/devel/linux-3/jdelvare-dmi/
> >>
> >> First 2
Hi Jean,
On 17.04.15 13:11, Ivan.khoronzhuk wrote:
On 17.04.15 11:54, Jean Delvare wrote:
Hi Ivan,
On Thu, 16 Apr 2015 23:16:59 +0300, Ivan.khoronzhuk wrote:
On 16.04.15 11:35, Jean Delvare wrote:
On Wed, 15 Apr 2015 15:35:30 +0100, Matt Fleming wrote:
Jean, do you want me to pick this
On 17.04.15 11:54, Jean Delvare wrote:
Hi Ivan,
On Thu, 16 Apr 2015 23:16:59 +0300, Ivan.khoronzhuk wrote:
On 16.04.15 11:35, Jean Delvare wrote:
On Wed, 15 Apr 2015 15:35:30 +0100, Matt Fleming wrote:
Jean, do you want me to pick this patch up or are you going to?
Good question, we need
Hi Ivan,
On Thu, 16 Apr 2015 23:16:59 +0300, Ivan.khoronzhuk wrote:
> On 16.04.15 11:35, Jean Delvare wrote:
> > On Wed, 15 Apr 2015 15:35:30 +0100, Matt Fleming wrote:
> >> Jean, do you want me to pick this patch up or are you going to?
> > Good question, we need to agree on a strategy.
> >
> >
Hi Ivan,
On Thu, 16 Apr 2015 23:16:59 +0300, Ivan.khoronzhuk wrote:
On 16.04.15 11:35, Jean Delvare wrote:
On Wed, 15 Apr 2015 15:35:30 +0100, Matt Fleming wrote:
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
On Fri, 17 Apr 2015 15:04:23 +0300, Ivan.khoronzhuk wrote:
On 17.04.15 13:11, Ivan.khoronzhuk wrote:
On 17.04.15 11:54, Jean Delvare wrote:
I have no formal tree yet, but my current patch set can be seen at:
http://jdelvare.nerim.net/devel/linux-3/jdelvare-dmi/
First 2 patches from you
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
On 17.04.15 11:54, Jean Delvare wrote:
Hi Ivan,
On Thu, 16 Apr 2015 23:16:59 +0300, Ivan.khoronzhuk wrote:
On 16.04.15 11:35, Jean Delvare wrote:
On Wed, 15 Apr 2015 15:35:30 +0100, Matt Fleming wrote:
Jean, do you want me to pick this patch up or are you going to?
Good question, we need
Hi Jean,
On 17.04.15 13:11, Ivan.khoronzhuk wrote:
On 17.04.15 11:54, Jean Delvare wrote:
Hi Ivan,
On Thu, 16 Apr 2015 23:16:59 +0300, Ivan.khoronzhuk wrote:
On 16.04.15 11:35, Jean Delvare wrote:
On Wed, 15 Apr 2015 15:35:30 +0100, Matt Fleming wrote:
Jean, do you want me to pick this
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
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"
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
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
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
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
On Thu, 2 Apr 2015 15:57:01 +0300, 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:
On Thu, 2 Apr 2015 15:57:01 +0300, 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
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
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
---
drivers/firmware/dmi_scan.c | 10 +-
1
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.khoronz...@globallogic.com
---
22 matches
Mail list logo
