linux-kernel - linux-next: manual merge of the notifications tree with the keys 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: <20210122160857.3e2939de@canb.auug.org.au>
Date:   Fri, 22 Jan 2021 16:08:57 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     David Howells <dhowells@...hat.com>
Cc:     Gabriel Krisman Bertazi <krisman@...labora.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the notifications tree with the keys
 tree

Hi all,

Today's linux-next merge of the notifications tree got conflicts in:

  Documentation/security/keys/core.rst
  samples/Kconfig
  samples/watch_queue/watch_test.c
  security/keys/Kconfig

between commit:

  0c3f19da1229 ("watch_queue: Drop references to /dev/watch_queue")

from the keys tree and commit:

  e3bc554d80d3 ("watch_queue: Clean up references to /dev/watch_queue")

from the notifications tree.

I fixed it up (in each file I used the latter's version of the
conflicted text) 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