public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David Gow <davidgow@google.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Brendan Higgins <brendanhiggins@google.com>,
	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: Re: linux-next: manual merge of the kunit-next tree with the mm tree
Date: Thu, 10 Oct 2024 13:21:16 -0700	[thread overview]
Message-ID: <20241010132116.45f077b8a819ddd46ee36132@linux-foundation.org> (raw)
In-Reply-To: <CABVgOSmbSzcGUi=E4piSojh3A4_0GjE0fAYbqKjtYGbE9beYRQ@mail.gmail.com>

On Thu, 10 Oct 2024 17:32:33 +0800 David Gow <davidgow@google.com> wrote:

> On Thu, 10 Oct 2024 at 05:36, Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > On Wed, 9 Oct 2024 15:00:19 -0600 Shuah Khan <skhan@linuxfoundation.org> wrote:
> >
> > > > 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.
> > >
> > > Andrew,
> > >
> > > I dropped this one from linux-kselftest kunit branch.
> > > The link to this patch if it isn't in your Inbox:
> > >
> > > https://lore.kernel.org/all/20240924032200.167622-1-luis.hernandez093@gmail.com/
> > > >
> > > > Adding David as well for feedback on this
> > >
> > > David, I think lib/ kunit patches can go through Andrew's tree.
> > > Renaming is causing merge conflicts.
> > >
> >
> > Cool.  David, I think it's simplest to just resend everything please.
> 
> No worries: a few of these patches need some small fixes / rebases
> anyway, so I'll make sure those happen and send them all as one
> series.
> 
> Would you rather this be based on 6.12-rc1, or on the current
> mm-nonmm-unstable branch, which has a couple of test changes already?

The latter would be convenient, thanks.

  reply	other threads:[~2024-10-10 20:21 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
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 [this message]
  -- 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=20241010132116.45f077b8a819ddd46ee36132@linux-foundation.org \
    --to=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=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