public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: 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>,
	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 10:28:45 -0600	[thread overview]
Message-ID: <b005d39f-2b75-4a26-a78c-5cd8f7076399@linuxfoundation.org> (raw)
In-Reply-To: <20241009162719.0adaea37@canb.auug.org.au>

On 10/8/24 23:27, Stephen Rothwell wrote:
> 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.
> 

Andrew,
Another one related to move from lib/ lib/tests/

If you would like to take these patches - it is perfectly
fine with me. If not I can handle these.

Adding David as well for feedback on this

thanks,
-- Shuah

  reply	other threads:[~2024-10-09 16:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  5:27 linux-next: manual merge of the kunit-next tree with the mm tree Stephen Rothwell
2024-10-09 16:28 ` Shuah Khan [this message]
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=b005d39f-2b75-4a26-a78c-5cd8f7076399@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=brendanhiggins@google.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 \
    --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