linux-kernel - Re: linux-next: duplicate patch in the tee tree

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] [day] [month] [year] [list]

Message-ID: <CAHUa44H+u6E9EEyLGKK1wgoA0i1At6-VUacV=ovxjumsQos17Q@mail.gmail.com>
Date: Tue, 5 Mar 2024 08:30:34 +0100
From: Jens Wiklander <jens.wiklander@...aro.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Olof Johansson <olof@...om.net>, 
	ARM <linux-arm-kernel@...ts.infradead.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-next <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the tee tree

On Tue, Mar 5, 2024 at 7:44 AM Arnd Bergmann <arnd@...db.de> wrote:
>
> On Tue, Mar 5, 2024, at 00:07, Stephen Rothwell wrote:
> > Hi all,
> >
> > The following commit is also in the arm-soc tree as a different commit
> > (but the same patch):
> >
> >   1d044941d538 ("tee: make tee_bus_type const")
>
> Thanks, this was intentional as I ended up cherry-picking the commit
> instead of merging. I expect that Jens will drop this branch now.

Yes, I've reset my next branch now.

Cheers,
Jens