Observing this also for the first time:
CC crypto/async_tx/async_xor.o
crypto/async_tx/async_xor.c: In function ‘async_xor_init’:
crypto/async_tx/async_xor.c:310: error: size of array ‘type name’ is
negative
make[2]: *** [crypto/async_tx/async_xor.o] Error 1
make[1]: *** [crypto/async_tx] Err
* Herbert Xu | 2009-04-21 18:53:27 [+0800]:
>It was already renamed in the original patch. The problem here
>is that padlock-aes was incorrectly renamed as it doesn't require
>a fallback.
Right, just key computation which is not part of the crypto API.
>Cheers,
>--
Sebastian
--
To unsubscribe
On Tue, Apr 21, 2009 at 10:26:45AM +0200, Sebastian Andrzej Siewior wrote:
>
> You changed all algos which need fallback to *-all to get them
> probed/loaded after the generic algorithm. The same load/fallback/test
> pattern exist for the s390 aes for instance. Should it be renamed as
> well?
It w
* Herbert Xu | 2009-04-21 13:56:13 [+0800]:
>On Tue, Apr 21, 2009 at 01:53:31PM +0800, Herbert Xu wrote:
>>
>> Thanks for the report. This patch should fix the problem.
>
>In fact, padlock-aes shouldn't have been aes-all in the first
>place so I'm going to add tihs patch too.
You changed all alg
