On 05/10/2018 01:57 PM, NeilBrown wrote:
> On Thu, May 10 2018, Marek Vasut wrote:
>
>> On 05/10/2018 12:28 AM, NeilBrown wrote:
>>> On Wed, May 09 2018, Boris Brezillon wrote:
>>>
On Fri, 27 Apr 2018 16:18:05 +1000
NeilBrown wrote:
> Hi,
> I've labeled this an RFC because
On Thu, May 10 2018, Marek Vasut wrote:
> On 05/10/2018 12:28 AM, NeilBrown wrote:
>> On Wed, May 09 2018, Boris Brezillon wrote:
>>
>>> On Fri, 27 Apr 2018 16:18:05 +1000
>>> NeilBrown wrote:
>>>
Hi,
I've labeled this an RFC because I'm really not sure about removing the
error
On 05/10/2018 12:28 AM, NeilBrown wrote:
> On Wed, May 09 2018, Boris Brezillon wrote:
>
>> On Fri, 27 Apr 2018 16:18:05 +1000
>> NeilBrown wrote:
>>
>>> Hi,
>>> I've labeled this an RFC because I'm really not sure about removing the
>>> error path from spi_nor_write() -- maybe that really matt
On Wed, May 09 2018, Boris Brezillon wrote:
> On Fri, 27 Apr 2018 16:18:05 +1000
> NeilBrown wrote:
>
>> Hi,
>> I've labeled this an RFC because I'm really not sure about removing the
>> error path from spi_nor_write() -- maybe that really matters. But on
>> my hardware, performing multiple s
On Fri, 27 Apr 2018 16:18:05 +1000
NeilBrown wrote:
> Hi,
> I've labeled this an RFC because I'm really not sure about removing the
> error path from spi_nor_write() -- maybe that really matters. But on
> my hardware, performing multiple small spi writes to the flash seems
> to work.
>
> T
Hi,
I've labeled this an RFC because I'm really not sure about removing the
error path from spi_nor_write() -- maybe that really matters. But on
my hardware, performing multiple small spi writes to the flash seems
to work.
The spi driver is drivers/staging/mt7621-spi. Possibly this needs t
6 matches
Mail list logo