On Wed, May 31, 2017 at 5:08 PM, David Miller wrote:
> From: Daniel Vetter
> Date: Wed, 31 May 2017 08:10:45 +0200
>
>> On Wed, May 31, 2017 at 7:54 AM, Daniel Vetter
>> wrote:
>>> On Wed, May 31, 2017 at 1:06 AM, Dave Airlie
On Wed, 31 May 2017, David Miller wrote:
> And we can't understand why respinning with the requested change is
> less work than making several postings such as this one.
When our CI hits tons of non-drm issues every merge window, I imagine
our developers can start to get a
From: Daniel Vetter
Date: Wed, 31 May 2017 08:10:45 +0200
> On Wed, May 31, 2017 at 7:54 AM, Daniel Vetter wrote:
>> On Wed, May 31, 2017 at 1:06 AM, Dave Airlie wrote:
>>> On 31 May 2017 at 08:10, David Miller
On Wed, May 31, 2017 at 7:54 AM, Daniel Vetter wrote:
> On Wed, May 31, 2017 at 1:06 AM, Dave Airlie wrote:
>> On 31 May 2017 at 08:10, David Miller wrote:
>>> From: Daniel Vetter
>>> Date: Tue, 30 May 2017
On Wed, May 31, 2017 at 1:06 AM, Dave Airlie wrote:
> On 31 May 2017 at 08:10, David Miller wrote:
>> From: Daniel Vetter
>> Date: Tue, 30 May 2017 22:15:42 +0200
>>
>>> If the e1000e maintainer wants to coalesce or not return
On 31 May 2017 at 08:10, David Miller wrote:
> From: Daniel Vetter
> Date: Tue, 30 May 2017 22:15:42 +0200
>
>> If the e1000e maintainer wants to coalesce or not return statements
>> this simple way, that's imo on him to change the color as needed.
>
From: Daniel Vetter
Date: Tue, 30 May 2017 22:15:42 +0200
> If the e1000e maintainer wants to coalesce or not return statements
> this simple way, that's imo on him to change the color as needed.
That's not how things work.
If the maintainer wants you to style things a
Hi Dave (both of them),
topic/e1000e-fix-2017-05-30:
Just an e1000e crash fix that somehow got stuck in a trivial bikeshed,
see
https://patchwork.ozlabs.org/patch/729312/
Sending this your way since not even the intel-internal escalation seems
to have worked out. If the e1000e maintainer wants