[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231103092134.7ddde5c3@canb.auug.org.au>
Date: Fri, 3 Nov 2023 09:21:34 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Shuah Khan <shuah@...nel.org>,
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: Re: linux-next: manual merge of the kselftest tree with the
mm-hotfixes tree
Hi all,
On Thu, 19 Oct 2023 16:33:10 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> 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 file from the latter commit) and can carry the
> fix as necessary. This is now fxed 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.
This is now a conflict between the mm-hotfixes tree and Linus' tree.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists