On Mon, May 22, 2017 at 9:47 PM, Jan Kiszka wrote:
> On 2017-05-22 20:37, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 9:23 PM, Lee Jones wrote:
>>> On Mon, 22 May 2017, Andy Shevchenko wrote:
On Mon, May 22, 2017 at 8:38 PM, Jan Kiszka
On Mon, May 22, 2017 at 9:47 PM, Jan Kiszka wrote:
> On 2017-05-22 20:37, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 9:23 PM, Lee Jones wrote:
>>> On Mon, 22 May 2017, Andy Shevchenko wrote:
On Mon, May 22, 2017 at 8:38 PM, Jan Kiszka wrote:
>> Got your point.
>> Jan, care to
On 2017-05-22 20:37, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 9:23 PM, Lee Jones wrote:
>> On Mon, 22 May 2017, Andy Shevchenko wrote:
>>> On Mon, May 22, 2017 at 8:38 PM, Jan Kiszka wrote:
On 2017-05-22 19:36, Andy Shevchenko wrote:
>
On 2017-05-22 20:37, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 9:23 PM, Lee Jones wrote:
>> On Mon, 22 May 2017, Andy Shevchenko wrote:
>>> On Mon, May 22, 2017 at 8:38 PM, Jan Kiszka wrote:
On 2017-05-22 19:36, Andy Shevchenko wrote:
>
Then let's leave the decision up to the
On Mon, May 22, 2017 at 9:23 PM, Lee Jones wrote:
> On Mon, 22 May 2017, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 8:38 PM, Jan Kiszka wrote:
>> > On 2017-05-22 19:36, Andy Shevchenko wrote:
>> > Then let's leave the decision up to the
On Mon, May 22, 2017 at 9:23 PM, Lee Jones wrote:
> On Mon, 22 May 2017, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 8:38 PM, Jan Kiszka wrote:
>> > On 2017-05-22 19:36, Andy Shevchenko wrote:
>> > Then let's leave the decision up to the maintainer.
>>
>> Lee, just for your convenience
On Mon, 22 May 2017, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 8:38 PM, Jan Kiszka wrote:
> > On 2017-05-22 19:36, Andy Shevchenko wrote:
> >> On Mon, May 22, 2017 at 8:34 PM, Jan Kiszka wrote:
> >>> On 2017-05-22 19:26, Andy Shevchenko
On Mon, 22 May 2017, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 8:38 PM, Jan Kiszka wrote:
> > On 2017-05-22 19:36, Andy Shevchenko wrote:
> >> On Mon, May 22, 2017 at 8:34 PM, Jan Kiszka wrote:
> >>> On 2017-05-22 19:26, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 8:25 PM, Jan
On Mon, May 22, 2017 at 8:38 PM, Jan Kiszka wrote:
> On 2017-05-22 19:36, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 8:34 PM, Jan Kiszka wrote:
>>> On 2017-05-22 19:26, Andy Shevchenko wrote:
On Mon, May 22, 2017 at 8:25 PM, Jan Kiszka
On Mon, May 22, 2017 at 8:38 PM, Jan Kiszka wrote:
> On 2017-05-22 19:36, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 8:34 PM, Jan Kiszka wrote:
>>> On 2017-05-22 19:26, Andy Shevchenko wrote:
On Mon, May 22, 2017 at 8:25 PM, Jan Kiszka wrote:
> On 2017-05-22 19:20, Andy
On 2017-05-22 19:36, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 8:34 PM, Jan Kiszka wrote:
>> On 2017-05-22 19:26, Andy Shevchenko wrote:
>>> On Mon, May 22, 2017 at 8:25 PM, Jan Kiszka wrote:
On 2017-05-22 19:20, Andy Shevchenko wrote:
On 2017-05-22 19:36, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 8:34 PM, Jan Kiszka wrote:
>> On 2017-05-22 19:26, Andy Shevchenko wrote:
>>> On Mon, May 22, 2017 at 8:25 PM, Jan Kiszka wrote:
On 2017-05-22 19:20, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 8:18 PM, Jan
On Mon, May 22, 2017 at 8:34 PM, Jan Kiszka wrote:
> On 2017-05-22 19:26, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 8:25 PM, Jan Kiszka wrote:
>>> On 2017-05-22 19:20, Andy Shevchenko wrote:
On Mon, May 22, 2017 at 8:18 PM, Jan Kiszka
On Mon, May 22, 2017 at 8:34 PM, Jan Kiszka wrote:
> On 2017-05-22 19:26, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 8:25 PM, Jan Kiszka wrote:
>>> On 2017-05-22 19:20, Andy Shevchenko wrote:
On Mon, May 22, 2017 at 8:18 PM, Jan Kiszka wrote:
> On 2017-05-22 19:12, Andy
On 2017-05-22 19:26, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 8:25 PM, Jan Kiszka wrote:
>> On 2017-05-22 19:20, Andy Shevchenko wrote:
>>> On Mon, May 22, 2017 at 8:18 PM, Jan Kiszka wrote:
On 2017-05-22 19:12, Andy Shevchenko wrote:
On 2017-05-22 19:26, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 8:25 PM, Jan Kiszka wrote:
>> On 2017-05-22 19:20, Andy Shevchenko wrote:
>>> On Mon, May 22, 2017 at 8:18 PM, Jan Kiszka wrote:
On 2017-05-22 19:12, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 1:53 PM, Jan
On Mon, May 22, 2017 at 8:25 PM, Jan Kiszka wrote:
> On 2017-05-22 19:20, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 8:18 PM, Jan Kiszka wrote:
>>> On 2017-05-22 19:12, Andy Shevchenko wrote:
On Mon, May 22, 2017 at 1:53 PM, Jan Kiszka
On Mon, May 22, 2017 at 8:25 PM, Jan Kiszka wrote:
> On 2017-05-22 19:20, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 8:18 PM, Jan Kiszka wrote:
>>> On 2017-05-22 19:12, Andy Shevchenko wrote:
On Mon, May 22, 2017 at 1:53 PM, Jan Kiszka wrote:
> Avoids reimplementation of DMI
On 2017-05-22 19:20, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 8:18 PM, Jan Kiszka wrote:
>> On 2017-05-22 19:12, Andy Shevchenko wrote:
>>> On Mon, May 22, 2017 at 1:53 PM, Jan Kiszka wrote:
Avoids reimplementation of DMI matching in
On 2017-05-22 19:20, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 8:18 PM, Jan Kiszka wrote:
>> On 2017-05-22 19:12, Andy Shevchenko wrote:
>>> On Mon, May 22, 2017 at 1:53 PM, Jan Kiszka wrote:
Avoids reimplementation of DMI matching in intel_quark_i2c_setup.
>>>
>>> What's wrong with
On Mon, May 22, 2017 at 8:18 PM, Jan Kiszka wrote:
> On 2017-05-22 19:12, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 1:53 PM, Jan Kiszka wrote:
>>> Avoids reimplementation of DMI matching in intel_quark_i2c_setup.
>>
>> What's wrong with
On Mon, May 22, 2017 at 8:18 PM, Jan Kiszka wrote:
> On 2017-05-22 19:12, Andy Shevchenko wrote:
>> On Mon, May 22, 2017 at 1:53 PM, Jan Kiszka wrote:
>>> Avoids reimplementation of DMI matching in intel_quark_i2c_setup.
>>
>> What's wrong with current approach? I suppose this will make sense
>>
On 2017-05-22 19:12, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 1:53 PM, Jan Kiszka wrote:
>> Avoids reimplementation of DMI matching in intel_quark_i2c_setup.
>
> What's wrong with current approach? I suppose this will make sense
> when we will have an issue /
On 2017-05-22 19:12, Andy Shevchenko wrote:
> On Mon, May 22, 2017 at 1:53 PM, Jan Kiszka wrote:
>> Avoids reimplementation of DMI matching in intel_quark_i2c_setup.
>
> What's wrong with current approach? I suppose this will make sense
> when we will have an issue / impediment. Right now it
On Mon, May 22, 2017 at 1:53 PM, Jan Kiszka wrote:
> Avoids reimplementation of DMI matching in intel_quark_i2c_setup.
What's wrong with current approach? I suppose this will make sense
when we will have an issue / impediment. Right now it looks like
over-engineering.
On Mon, May 22, 2017 at 1:53 PM, Jan Kiszka wrote:
> Avoids reimplementation of DMI matching in intel_quark_i2c_setup.
What's wrong with current approach? I suppose this will make sense
when we will have an issue / impediment. Right now it looks like
over-engineering.
(Yes, I know what I said
26 matches
Mail list logo