linux-kernel - Re: linux-next: duplicate patch in the sysctl 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: <20231011083612.4hymwsvc43hrwm6h@localhost>
Date:   Wed, 11 Oct 2023 10:36:12 +0200
From:   Joel Granados <j.granados@...sung.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Luis Chamberlain <mcgrof@...nel.org>
CC:     Jens Axboe <axboe@...nel.dk>,
        Phillip Potter <phil@...lpotter.co.uk>,
        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 sysctl tree

On Wed, Oct 11, 2023 at 04:20:50PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the block tree as a different commit
> (but the same patch):
> 
>   80f3c6cfab37 ("cdrom: Remove now superfluous sentinel element from ctl_table array")
> 
> This is commit
> 
>   114b0ff62a65 ("cdrom: Remove now superfluous sentinel element from ctl_table array")
> 
> in the block tree.
Is this a warning on the merge? or did it actually error out? if it is a
wraning and one of the two was skipped, it can be safely ignored as they
are the same. I can also remove that commit from my set and send another
version. @luis: How do you want to handle it?

-- 

Joel Granados

Download attachment "signature.asc" of type "application/pgp-signature" (660 bytes)