linux-kernel - Re: [PATCHv8 0/3] optee: register drivers on optee bus

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]

Message-ID: <20200623005034.GC28795@linux.intel.com>
Date:   Tue, 23 Jun 2020 03:50:34 +0300
From:   Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To:     Jens Wiklander <jens.wiklander@...aro.org>
Cc:     Maxim Uvarov <maxim.uvarov@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "tee-dev @ lists . linaro . org" <tee-dev@...ts.linaro.org>,
        peterhuewe@....de, Jason Gunthorpe <jgg@...pe.ca>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-integrity@...r.kernel.org, Arnd Bergmann <arnd@...aro.org>,
        Sumit Garg <sumit.garg@...aro.org>
Subject: Re: [PATCHv8 0/3] optee: register drivers on optee bus

On Thu, Jun 18, 2020 at 09:56:13AM +0200, Jens Wiklander wrote:
> On Thu, Jun 18, 2020 at 02:37:55AM +0300, Jarkko Sakkinen wrote:
> > On Tue, Jun 16, 2020 at 10:29:07AM +0200, Jens Wiklander wrote:
> > > Hi Maxim and Jarkko,
> > > 
> > > On Mon, Jun 15, 2020 at 05:32:40PM +0300, Maxim Uvarov wrote:
> > > > ping.
> > > > Patchset was reviewed and all comments are codeverd. Optee-os patches
> > > > were merged. These kernel patches look like they are hanging
> > > > somewhere...
> > > 
> > > I'm almost OK with this patchset, except that
> > > Documentation/ABI/testing/sysfs-bus-optee-devices needs to be updated
> > > for the new kernel version and TEE mailing list which we're changing right
> > > now.
> > > 
> > > The last patch touches files I'm not maintainer of. That patch depends
> > > on the previous patches so it makes sense to keep them together.  If a
> > > TPM device driver maintainer would ack that patch I can take it via my
> > > tree. Or we can do it the other way around (with a v9 patchset),
> > > whichever is preferred.
> > > 
> > > Cheers,
> > > Jens
> > 
> > Probably easier if you pick all three and I ack the one touching TPM.
> 
> Makes sense, let's do that.

Great, thanks!

/Jarkko