This is a note to let you know that I have just added a patch titled
crypto: ux500 - make interrupt mode plausible
to the linux-3.13.y-queue branch of the 3.13.y.z extended stable tree
which can be found at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;a=shortlog;h=refs/heads/linux-3.1
On Thursday 03 July 2014 21:44:00 Herbert Xu wrote:
>
> > The bug has existed since the driver was first merged, and was
> > probably never detected because nobody tried to use interrupt mode.
> > It might make sense to backport this fix to stable kernels, depending
> > on how the crypto maintaine
On Thu, Jun 26, 2014 at 01:43:02PM +0200, Arnd Bergmann wrote:
> The interrupt handler in the ux500 crypto driver has an obviously
> incorrect way to access the data buffer, which for a while has
> caused this build warning:
>
> ../ux500/cryp/cryp_core.c: In function 'cryp_interrupt_handler':
> ..
The interrupt handler in the ux500 crypto driver has an obviously
incorrect way to access the data buffer, which for a while has
caused this build warning:
../ux500/cryp/cryp_core.c: In function 'cryp_interrupt_handler':
../ux500/cryp/cryp_core.c:234:5: warning: passing argument 1 of '__fswab32'
