lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 3 Jul 2018 17:49:16 +0900
From:   Alexandre Courbot <acourbot@...omium.org>
To:     Stanimir Varbanov <stanimir.varbanov@...aro.org>
Cc:     Mauro Carvalho Chehab <mchehab@...nel.org>,
        Hans Verkuil <hverkuil@...all.nl>,
        Linux Media Mailing List <linux-media@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-arm-msm@...r.kernel.org, vgarodia@...eaurora.org,
        Tomasz Figa <tfiga@...omium.org>
Subject: Re: [PATCH v4 00/27] Venus updates

On Tue, Jul 3, 2018 at 12:25 AM Stanimir Varbanov
<stanimir.varbanov@...aro.org> wrote:
>
> Hi Alex,
>
> Thanks for review comments!
>
> On 07/02/2018 11:45 AM, Alexandre Courbot wrote:
> > Hi Stanimir,
> >
> > Thanks for this very well organized series and sorry for not giving
> > feedback earlier.
> >
> > I have tested this version against the 4.14 Chrome OS kernel tree (+ a
> > few extra changes to comply with the codec API) and it was working
> > flawlessly.
> >
> > Therefore,
> >
> > Tested-by: Alexandre Courbot <acourbot@...omium.org>
>
> Thanks for testing!
>
> >
> > For the whole series.
> >
> > I have a few comments/questions on some patches, would be great if you
> > could take a look. Also wondering what is your plan regarding codec
> > API compliance? Do you plan to integrate it into the current series,
> > or work on it after merging this initial work? Both ways would be ok
> > as far as I am concerned.
>
> Unfortunately I'm not ready with codec API compliance (at least for
> Venus v1 & v3). I'm working on that intensively these days and I'd say
> with a good progress but I still have few issues/details which needs
> more attention and time.
>
> So I guess the plan minimum is to merge this series first.

I'm fine with that. That will also allow us to tune the Codec API spec
using this driver as reference.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ