Hi Boris,
On 30.05.2018 16:32, Boris Brezillon wrote:
Hi Frieder,
On Wed, 30 May 2018 15:14:30 +0200
Frieder Schrempf wrote:
When porting (Q)SPI controller drivers from the MTD layer to the SPI
layer, the naming scheme for the memory devices changes. To be able
to keep compatibility with
Hi Boris,
On 30.05.2018 16:32, Boris Brezillon wrote:
Hi Frieder,
On Wed, 30 May 2018 15:14:30 +0200
Frieder Schrempf wrote:
When porting (Q)SPI controller drivers from the MTD layer to the SPI
layer, the naming scheme for the memory devices changes. To be able
to keep compatibility with
Hi Frieder,
On Wed, 30 May 2018 15:14:30 +0200
Frieder Schrempf wrote:
> When porting (Q)SPI controller drivers from the MTD layer to the SPI
> layer, the naming scheme for the memory devices changes. To be able
> to keep compatibility with the old drivers naming scheme, a function
> is added
Hi Frieder,
On Wed, 30 May 2018 15:14:30 +0200
Frieder Schrempf wrote:
> When porting (Q)SPI controller drivers from the MTD layer to the SPI
> layer, the naming scheme for the memory devices changes. To be able
> to keep compatibility with the old drivers naming scheme, a function
> is added
When porting (Q)SPI controller drivers from the MTD layer to the SPI
layer, the naming scheme for the memory devices changes. To be able
to keep compatibility with the old drivers naming scheme, a function
is added to the SPI mem interface to let controller drivers set a
custom name for the
When porting (Q)SPI controller drivers from the MTD layer to the SPI
layer, the naming scheme for the memory devices changes. To be able
to keep compatibility with the old drivers naming scheme, a function
is added to the SPI mem interface to let controller drivers set a
custom name for the
6 matches
Mail list logo