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

Message-ID: <20200113123603.33c957e1@canb.auug.org.au>
Date:   Mon, 13 Jan 2020 12:36:03 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     David Howells <dhowells@...hat.com>,
        Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Kars de Jong <jongk@...ux-m68k.org>
Subject: linux-next: manual merge of the keys tree with the m86k tree

Hi all,

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

  arch/m68k/kernel/syscalls/syscall.tbl

between commit:

  e8bb2a2a1d51 ("m68k: Wire up clone3() syscall")

from the m86k tree and commit:

  519c484a997a ("Add a general, global device notification watch list")

from the keys tree.

I fixed it up (see below) 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