linux-kernel - linux-next: manual merge of the kspp tree with the kbuild 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: <20210826164809.402222af@canb.auug.org.au>
Date:   Thu, 26 Aug 2021 16:48:09 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Kees Cook <keescook@...omium.org>,
        Masahiro Yamada <masahiroy@...nel.org>
Cc:     "Gustavo A. R. Silva" <gustavoars@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Nick Desaulniers <ndesaulniers@...gle.com>
Subject: linux-next: manual merge of the kspp tree with the kbuild tree

Hi all,

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

  Makefile

between commit:

  389640bf8d17 ("Makefile: remove stale cc-option checks")

from the kbuild tree and commits:

  2d931b634b81 ("Makefile: Enable -Warray-bounds")
  7d8aac16a0a8 ("Makefile: Enable -Wzero-length-bounds")

from the kspp tree.

I fixed it up (the latter removed the line modified by the former,
so 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