From: Andrew Morton <akpm@linux-foundation.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Brendan Higgins <brendanhiggins@google.com>,
Jeff Johnson <quic_jjohnson@quicinc.com>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the kunit-next tree
Date: Mon, 17 Jun 2024 12:30:46 -0700 [thread overview]
Message-ID: <20240617123046.51171b70e613606212c92b5a@linux-foundation.org> (raw)
In-Reply-To: <46645216-dcb7-45d6-83c5-fdd9451362ff@linuxfoundation.org>
On Mon, 17 Jun 2024 13:21:25 -0600 Shuah Khan <skhan@linuxfoundation.org> wrote:
> Hi Andrew,
>
> On 6/10/24 23:22, Stephen Rothwell wrote:
> > Hi all,
> >
> > The following commit is also in the mm tree as a different commit (but
> > the same patch):
> >
> > 425ae3ab5a1f ("list: test: add the missing MODULE_DESCRIPTION() macro")
> > > This is commit
> >
> > 245e5db4adaf ("lib/list_test: add the missing MODULE_DESCRIPTION() macro")
> >
> > in the mm-nonmm-unstable branch of the mm tree.
> >
>
> Can you drop the patch from mm tree? It will help avoid merge conflicts
> in case there are other KUnit patches that depend on this end up in
> kunit-next.
I dropped this from mm.git on June 11.
next prev parent reply other threads:[~2024-06-17 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 5:22 linux-next: duplicate patch in the kunit-next tree Stephen Rothwell
2024-06-17 19:21 ` Shuah Khan
2024-06-17 19:30 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-13 4:25 Stephen Rothwell
2025-01-13 5:21 ` Greg KH
2025-01-13 22:45 ` Shuah Khan
2025-01-14 7:28 ` Greg KH
2023-12-11 21:01 Stephen Rothwell
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=20240617123046.51171b70e613606212c92b5a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=brendanhiggins@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@treblig.org \
--cc=quic_jjohnson@quicinc.com \
--cc=sfr@canb.auug.org.au \
--cc=skhan@linuxfoundation.org \
/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