Hi Vignesh,
On 11/14/18 6:00 AM, Vignesh R wrote:
Hi,
On 13/11/18 11:02 PM, thor.tha...@linux.intel.com wrote:
From: Thor Thayer
The current Cadence QSPI driver caused a kernel panic sporadically
when writing to QSPI. The problem was caused by writing more bytes
than needed because the QSPI
Hi,
On 13/11/18 11:02 PM, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> The current Cadence QSPI driver caused a kernel panic sporadically
> when writing to QSPI. The problem was caused by writing more bytes
> than needed because the QSPI operated on 4 bytes at a time.
>
> [ 11.2
Hi Marek,
On 03/19/2018 05:33 PM, Marek Vasut wrote:
On 03/19/2018 07:45 PM, thor.tha...@linux.intel.com wrote:
From: Thor Thayer
The current Cadence QSPI driver caused a kernel panic when loading
a Root Filesystem from QSPI. The problem was caused by reading more
bytes than needed because th
Hi Thor,
I love your patch! Perhaps something to improve:
[auto build test WARNING on v4.16-rc4]
[also build test WARNING on next-20180319]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/thor-t
Hi Thor,
I love your patch! Perhaps something to improve:
[auto build test WARNING on v4.16-rc4]
[also build test WARNING on next-20180319]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/thor-t
On 03/19/2018 07:45 PM, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> The current Cadence QSPI driver caused a kernel panic when loading
> a Root Filesystem from QSPI. The problem was caused by reading more
> bytes than needed because the QSPI operated on 4 bytes at a time.
>
> [
6 matches
Mail list logo
