On Fri, Jan 12, 2018 at 02:02:51PM +0100, Antoine Tenart wrote:
> Hi Herbert,
>
> On Fri, Dec 22, 2017 at 03:28:38PM +0100, Antoine Tenart wrote:
> > On Fri, Dec 22, 2017 at 08:11:54PM +1100, Herbert Xu wrote:
> > >
> > > Patches 1-16 applied. If patch 17 needs to go through the crypto
> > > tre
Hi Herbert,
On Fri, Dec 22, 2017 at 03:28:38PM +0100, Antoine Tenart wrote:
> On Fri, Dec 22, 2017 at 08:11:54PM +1100, Herbert Xu wrote:
> >
> > Patches 1-16 applied. If patch 17 needs to go through the crypto
> > tree please let me know.
>
> Thanks! Yes patch 17 should got through the crypto
Hi Herbert,
On Fri, Dec 22, 2017 at 08:11:54PM +1100, Herbert Xu wrote:
> On Thu, Dec 14, 2017 at 03:26:42PM +0100, Antoine Tenart wrote:
> >
> > This series depends on the previous one, "crypto: inside-secure - set of
> > fixes"[1]. The series contains various improvements to the Inside Secure
>
On Thu, Dec 14, 2017 at 03:26:42PM +0100, Antoine Tenart wrote:
> Hi Herbert,
>
> This series depends on the previous one, "crypto: inside-secure - set of
> fixes"[1]. The series contains various improvements to the Inside Secure
> SafeXcel driver, which are bundled in a single series to avoid any
Hi Herbert,
This series depends on the previous one, "crypto: inside-secure - set of
fixes"[1]. The series contains various improvements to the Inside Secure
SafeXcel driver, which are bundled in a single series to avoid any
conflict.
- Patches 1-4 are cosmetic fixes (typo, more comments and dead
