Hi, Hmm.. yes. in my first patch I had OMAP3 and 2 Should I send updated patch above that?
- Dmitry On 05/05/10 21:38, ext Tony Lindgren wrote: > * Herbert Xu <herb...@gondor.apana.org.au> [100502 20:07]: > >> On Wed, Apr 28, 2010 at 05:18:05PM +0300, Dmitry Kasatkin wrote: >> >>> Changes to v4: >>> - concurrent requests support via queue >>> - hmac >>> - shash support removed >>> >>> Dmitry Kasatkin (2): >>> crypto: updates omap sham device related platform code >>> crypto: omap-sham - omap sha1 & md5 driver >>> >> Both patches applied. Thanks for all your hard work Dmitry! >> > Just noticed that the first patch should be updated: > > CONFIG_ARCH_OMAP2 instead of CONFIG_ARCH_OMAP24XX > CONFIG_ARCH_OMAP3 instead of CONFIG_ARCH_OMAP34XX > > BTW, chances are that this part will conflict with other > omap patches. But if that happens, we can move it to > the omap for-next. > > Regards, > > Tony > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
