On Tue, 2008-12-23 at 21:01 +0800, Sebastian Andrzej Siewior wrote: > * Huang Ying | 2008-12-23 16:49:26 [+0800]: > > >If aes_x86_64 and aes_generic are compiled as builtin, the > >initialization order is undetermined. That is, aes_x86_64 may be > >initilized before aes_generic is initilized, but aes_x86_64 depends on > >tables generated in aes_generic initialization code. aes_x86_64 can > >not work before aes_generic is initialized, so that cause register > >time testing failed with following error message: > > Couldn't we link arch/x/crypto after crypto ? I think that is not easy. Not all architecture follow the same directory structure arch/<x>/crypto. And arch/x86/crypto is used by user mode linux too. Best Regards, Huang Ying
Attachment:
signature.asc
Description: This is a digitally signed message part
