linux-kernel - Re: linux-next: duplicate patch in the omap 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <7ha5cvcvdv.fsf@baylibre.com>
Date: Mon, 16 Dec 2024 10:53:16 -0800
From: Kevin Hilman <khilman@...libre.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>, Krzysztof Kozlowski
 <krzk@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the omap tree

Stephen Rothwell <sfr@...b.auug.org.au> writes:

> Hi all,
>
> The following commit is also in the drivers-memory tree as a different
> commit (but the same patch):
>
>   56d96fc55390 ("memory: omap-gpmc: deadcode a pair of functions")
>
> This is commit
>
>   5119e6b44f8a ("memory: omap-gpmc: deadcode a pair of functions")
>
> in the drivers-memory tree.

Yes, this one was my fault.  It's now dropped from the omap tree.

Kevin