linux-kernel - Re: linux-next: duplicate patch in the m68knommu 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <f0d0e8ad-8391-44f3-90e0-d2325daebb64@linux-m68k.org>
Date:   Mon, 9 Oct 2023 12:00:05 +1000
From:   Greg Ungerer <gerg@...ux-m68k.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Geert Uytterhoeven <geert@...ux-m68k.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 m68knommu tree

Hi Stephen,

On 9/10/23 10:16, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the m68k tree as a different commit
> (but the same patch):
> 
>    af580d01acc3 ("m68k: use kernel's generic libgcc functions")
> 
> The is commit
> 
>    a0938a8e2fb3 ("m68k: Use kernel's generic libgcc functions")
> 
> in the m68k tree.

Sorry, yes, fixed now. I removed it from the m68kmnommu git tree.

Regards
Greg