linux-kernel - linux-next: manual merge of the kselftest tree with the mm-hotfixes 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: <20231019163310.6c24d6ac@canb.auug.org.au>
Date:   Thu, 19 Oct 2023 16:33:10 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Shuah Khan <shuah@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Mark Brown <broonie@...nel.org>,
        Shuah Khan <skhan@...uxfoundation.org>,
        Tiezhu Yang <yangtiezhu@...ngson.cn>
Subject: linux-next: manual merge of the kselftest tree with the mm-hotfixes
 tree

Hi all,

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

  tools/testing/selftests/clone3/clone3.c

between commit:

  fc7f04dc23db ("selftests/clone3: Fix broken test under !CONFIG_TIME_NS")

from the mm-hotfixes tree and commit:

  34dce23f7e40 ("selftests/clone3: Report descriptive test names")

from the kselftest tree.

I fixed it up (I used this files form the latter commit) 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