[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170829.151217.629593058367678824.davem@davemloft.net>
Date: Tue, 29 Aug 2017 15:12:17 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: f.fainelli@...il.com
Cc: netdev@...r.kernel.org, opendmb@...il.com, andrew@...n.ch,
vivien.didelot@...oirfairelinux.com
Subject: Re: [PATCH net-next 0/4] Endian fixes for SYSTEMPORT/SF2/MDIO
From: Florian Fainelli <f.fainelli@...il.com>
Date: Tue, 29 Aug 2017 15:08:00 -0700
> On 08/29/2017 02:52 PM, David Miller wrote:
>> From: Florian Fainelli <f.fainelli@...il.com>
>> Date: Tue, 29 Aug 2017 14:45:30 -0700
>>
>>> On 08/29/2017 02:42 PM, David Miller wrote:
>>>> From: Florian Fainelli <f.fainelli@...il.com>
>>>> Date: Tue, 29 Aug 2017 11:39:41 -0700
>>>>
>>>>> While trying an ARM BE kernel for kinks, the 3 drivers below started not
>>>>> working and the reasons why became pretty obvious because the register space
>>>>> remains LE (hardwired), except for Broadcom MIPS where it follows the CPU's
>>>>> native endian (let's call that a feature).
>>>>
>>>> Series applied, thanks Florian.
>>>
>>> If you have not pushed yet, seems like not, can you check you applied v2
>>> of this patch series, in particular this patch:
>>>
>>> http://patchwork.ozlabs.org/patch/807296/
>>
>> If you didn't keep messing with the patchwork state of patches in my
>> queue this confusion would not have happened.
>>
>> I did happen to apply v2, but because of all of the confusion you keep
>> creating, I used the header message from v1.
>>
>> It's already pushed out so there is nothing we can do about it.
>>
>
> It's all good, thanks! /me goes updating netdev-FAQ.txt to mention not
> touching patchwork.
Thank you.
Powered by blists - more mailing lists