On Wed, Jul 4, 2018 at 8:32 PM, Stephen Rothwell wrote:
> I have just removed that commit from the linux-next copy of mmotm (it
> was actually commit 026f20c65973 since Andrew did another release
> yesterday).
Thanks, Stephen!
Hi all,
On Wed, 4 Jul 2018 10:41:17 -0600 Logan Gunthorpe wrote:
>
> On 7/4/2018 10:23 AM, Fabio Estevam wrote:
> > From: Fabio Estevam
> >
> > This reverts commit 46e4bf08f6388ba748597275012d715d5e1861e6.
> >
> > Commit 46e4bf08f6388 ("crypto: caam: cleanup CONFIG_64BIT ifdefs
> > when using
On 7/4/2018 10:23 AM, Fabio Estevam wrote:
> From: Fabio Estevam
>
> This reverts commit 46e4bf08f6388ba748597275012d715d5e1861e6.
>
> Commit 46e4bf08f6388 ("crypto: caam: cleanup CONFIG_64BIT ifdefs
> when using io{read|write}64") causes kernel crash on imx6 systems:
>
> [2.041187] caam_jr
From: Fabio Estevam
This reverts commit 46e4bf08f6388ba748597275012d715d5e1861e6.
Commit 46e4bf08f6388 ("crypto: caam: cleanup CONFIG_64BIT ifdefs
when using io{read|write}64") causes kernel crash on imx6 systems:
[2.041187] caam_jr 2101000.jr0: job ring error: irqstate: 0103
[2.049