linux-kernel - linux-next: manual merge of the staging tree with the staging.current 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>] [day] [month] [year] [list]

Message-ID: <20230119145622.1e8e0d37@canb.auug.org.au>
Date:   Thu, 19 Jan 2023 14:56:22 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Greg KH <greg@...ah.com>
Cc:     Arnd Bergmann <arnd@...db.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Umang Jain <umang.jain@...asonboard.com>
Subject: linux-next: manual merge of the staging tree with the
 staging.current tree

Hi all,

Today's linux-next merge of the staging tree got a conflict in:

  drivers/staging/vc04_services/include/linux/raspberrypi/vchiq.h

between commit:

  7d83299351fe ("staging: vchiq_arm: fix enum vchiq_status return types")

from the staging.current tree and commit:

  3ba317227aa4 ("staging: vc04_services: Replace vchiq_status return type to int")

from the staging tree.

Thanks for the heads up.

I fixed it up (I just used the latter) and can carry the fix as
necessary. This is now fixed as far as linux-next is concerned, but any
non trivial conflicts should be mentioned to your upstream maintainer
when your tree is submitted for merging.  You may also want to consider
cooperating with the maintainer of the conflicting tree to minimise any
particularly complex conflicts.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped