public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Brendan Higgins <brendanhiggins@google.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Kuan-Wei Chiu <visitorckw@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>
Subject: linux-next: manual merge of the kunit-next tree with the mm tree
Date: Wed, 9 Oct 2024 16:27:19 +1100	[thread overview]
Message-ID: <20241009162719.0adaea37@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]

Hi all,

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

  lib/Kconfig.debug

between commit:

  0f2016a962f0 ("lib/Kconfig.debug: move int_pow test option to runtime testing section")

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 (see 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.

-- 
Cheers,
Stephen Rothwell

diff --cc lib/Kconfig.debug
index 409dd193c09b,0d6c979f0bfd..000000000000
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@@ -2993,22 -2993,6 +2993,22 @@@ config TEST_OBJPOO
  
  	  If unsure, say N.
  
- config INT_POW_TEST
++config INT_POW_KUNIT_TEST
 +	tristate "Integer exponentiation (int_pow) test" if !KUNIT_ALL_TESTS
 +	depends on KUNIT
 +	default KUNIT_ALL_TESTS
 +	help
 +	  This option enables the KUnit test suite for the int_pow function,
 +	  which performs integer exponentiation. The test suite is designed to
 +	  verify that the implementation of int_pow correctly computes the power
 +	  of a given base raised to a given exponent.
 +
 +	  Enabling this option will include tests that check various scenarios
 +	  and edge cases to ensure the accuracy and reliability of the exponentiation
 +	  function.
 +
 +	  If unsure, say N
 +
  endif # RUNTIME_TESTING_MENU
  
  config ARCH_USE_MEMTEST

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-10-09  5:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  5:27 Stephen Rothwell [this message]
2024-10-09 16:28 ` linux-next: manual merge of the kunit-next tree with the mm tree 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
  -- strict thread matches above, loose matches on Subject: below --
2024-10-04  3:55 Stephen Rothwell
2024-10-09 15:11 ` Shuah Khan
2024-10-09 20:42   ` Andrew Morton
2024-10-09 21:04     ` Shuah Khan

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=20241009162719.0adaea37@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=brendanhiggins@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=luis.hernandez093@gmail.com \
    --cc=skhan@linuxfoundation.org \
    --cc=visitorckw@gmail.com \
    /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