From: Shuah Khan <skhan@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Brendan Higgins <brendanhiggins@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Gow <davidgow@google.com>
Cc: "Bruno Sobreira França" <brunofrancadevsec@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Luis Felipe Hernandez" <luis.hernandez093@gmail.com>,
"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: linux-next: manual merge of the kunit-next tree with the mm tree
Date: Wed, 9 Oct 2024 09:11:19 -0600 [thread overview]
Message-ID: <51d2cb33-c0d3-4837-a22c-9c42a7a4818e@linuxfoundation.org> (raw)
In-Reply-To: <20241004135527.1e2fc747@canb.auug.org.au>
On 10/3/24 21:55, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the kunit-next tree got conflicts in:
>
> lib/math/Makefile
> lib/math/tests/Makefile
>
> between commit:
>
> aa2cc84cfeb0 ("lib/math: add int_log test suite")
>
> from the mm-nonmm-unstable branch of the mm tree and commit:
>
> f099bda563dd ("lib: math: Move kunit tests into tests/ subdir")
>
> from the kunit-next tree.
>
> I fixed it up (I used the latter version of lib/math/Makefile and see
> below the signature by the patch immediately 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.
Sorry for the delay on this. Thank you for fixing this up.
Andrew,
Looks like we might see more conflicts between mm and kunit trees
with the move from lib/ lib/tests/
I dropped a couple of patches I couldn't apply. Would you like
me to drop this from kunit tree?
Adding David as well for feedback on this.
>
> rom: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Fri, 4 Oct 2024 13:51:56 +1000
> Subject: [PATCH] fix up for "lib: math: Move kunit tests into tests/ subdir"
>
> interacting with "lib/math: add int_log test suite" from the mm tree.
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> lib/Kconfig.debug | 2 +-
> lib/math/tests/Makefile | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 9ed36fec4390..d3e44b17876d 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -3105,7 +3105,7 @@ config INT_POW_KUNIT_TEST
>
> If unsure, say N
>
> -config INT_LOG_TEST
> +config INT_LOG_KUNIT_TEST
> tristate "Integer log (int_log) test" if !KUNIT_ALL_TESTS
> depends on KUNIT
> default KUNIT_ALL_TESTS
> diff --git a/lib/math/tests/Makefile b/lib/math/tests/Makefile
> index 64b9bfe3381d..89a266241e98 100644
> --- a/lib/math/tests/Makefile
> +++ b/lib/math/tests/Makefile
> @@ -2,6 +2,6 @@
>
> obj-$(CONFIG_DIV64_KUNIT_TEST) += div64_kunit.o
> obj-$(CONFIG_INT_POW_KUNIT_TEST) += int_pow_kunit.o
> -obj-$(CONFIG_INT_LOG_TEST) += int_log_kunit.o
> +obj-$(CONFIG_INT_LOG_KUNIT_TEST) += int_log_kunit.o
> obj-$(CONFIG_MULDIV64_KUNIT_TEST) += mul_u64_u64_div_u64_kunit.o
> obj-$(CONFIG_RATIONAL_KUNIT_TEST) += rational_kunit.o
thanks,
-- Shuah
next prev parent reply other threads:[~2024-10-09 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 3:55 linux-next: manual merge of the kunit-next tree with the mm tree Stephen Rothwell
2024-10-09 15:11 ` Shuah Khan [this message]
2024-10-09 20:42 ` Andrew Morton
2024-10-09 21:04 ` Shuah Khan
-- strict thread matches above, loose matches on Subject: below --
2024-10-09 5:27 Stephen Rothwell
2024-10-09 16:28 ` Shuah Khan
2024-10-09 21:00 ` Shuah Khan
2024-10-09 21:36 ` Andrew Morton
2024-10-10 9:32 ` David Gow
2024-10-10 20:21 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51d2cb33-c0d3-4837-a22c-9c42a7a4818e@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=brendanhiggins@google.com \
--cc=brunofrancadevsec@gmail.com \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luis.hernandez093@gmail.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox