On Wed, Mar 11, 2015 at 11:44:48AM +0100, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> On 06:32 Wed 11 Mar , Sascha Hauer wrote:
> > On Tue, Mar 10, 2015 at 03:28:12PM +0100, Jean-Christophe PLAGNIOL-VILLARD
> > wrote:
> > > Now you need to call digest_alloc and when you finish to use it
> > >
On 06:32 Wed 11 Mar , Sascha Hauer wrote:
> On Tue, Mar 10, 2015 at 03:28:12PM +0100, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
> > Now you need to call digest_alloc and when you finish to use it digest_free.
> >
> > We need this for upcomming aes encryption support and secure boot
> > as we
On Tue, Mar 10, 2015 at 03:28:12PM +0100, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> Now you need to call digest_alloc and when you finish to use it digest_free.
>
> We need this for upcomming aes encryption support and secure boot
> as we will need multiple instance of the same digest.
>
> Signe
On Tue, Mar 10, 2015 at 03:28:12PM +0100, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> Now you need to call digest_alloc and when you finish to use it digest_free.
>
> We need this for upcomming aes encryption support and secure boot
> as we will need multiple instance of the same digest.
>
> Signe
Now you need to call digest_alloc and when you finish to use it digest_free.
We need this for upcomming aes encryption support and secure boot
as we will need multiple instance of the same digest.
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
---
commands/digest.c | 3 ++-
common/digest.c
