[GIT PULL] mtd: spi-nor: Changes for 4.11

[Marek Vasut]

On 02/10/2017 06:56 PM, Heiner Kallweit wrote:
> Am 10.02.2017 um 14:07 schrieb Marek Vasut:
>> On 02/10/2017 07:39 AM, Heiner Kallweit wrote:
>>> Am 10.02.2017 um 03:46 schrieb Brian Norris:
>>>> On Wed, Feb 08, 2017 at 11:09:39AM -0800, Brian Norris wrote:
>>>>> On Wed, Feb 08, 2017 at 11:36:10AM +0100, Cyrille Pitchen wrote:
>>>>>> Le 08/02/2017 à 06:52, Heiner Kallweit a écrit :
>>>>>>> Am 08.02.2017 um 02:09 schrieb Marek Vasut:
>>>>>>>> On 02/07/2017 04:31 PM, Cyrille Pitchen wrote:
>>>>>> [...]
>>>>>>>>> Heiner Kallweit (1):
>>>>>>>>>       mtd: m25p80: consider max message size in m25p80_read
>>>>>>>>
>>>>>>>> I cannot say I'm super-happy about this particular patch, still ...
>>>>>>>>
>>>>>>> W/o it at least the fsl-espi driver is broken for transfers >= 64kB.
>>>>>>>
>>>> [...]
>>>>
>>>>> One thing I do object to: why is this change marked for stable? It's not
>>>>> our fault you broke your duct-taped-together SPI driver in 4.9. I don't
>>>>> think backporting features is the way to satisfy the -stable
>>>>> requirements. Maybe some reverts would be the right way...
>>>>
>>> The patch was submitted in Aug 2016 already and there was also an inquiry
>>> to get it into 4.9:
>>> http://lists.infradead.org/pipermail/linux-mtd/2016-September/069363.html
>>>
>>> But due to whatever circumstances nothing happened and there was no
>>> response.
>>
>> Is that a bugfix ?
>>
> Certain changes to the fsl-espi driver and the patch we're talking about
> here were supposed to go into the same kernel release.
> The driver changes made it to mainline months ago, the m25p80 patch not.
> So yes, we have a bug in 4.9, transfers >= 64k fail on fsl-espi.

Maybe the fsl-espi change should be reverted for 4.9 ...

-- 
Best regards,
Marek Vasut