From: Shuah Khan <skhan@linuxfoundation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Brendan Higgins" <brendanhiggins@google.com>,
"David Gow" <davidgow@google.com>,
"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 15:04:01 -0600 [thread overview]
Message-ID: <25172760-bb70-4343-b79f-8cd5f082122c@linuxfoundation.org> (raw)
In-Reply-To: <20241009134255.8083566505456b4f1159a6d2@linux-foundation.org>
On 10/9/24 14:42, Andrew Morton wrote:
> On Wed, 9 Oct 2024 09:11:19 -0600 Shuah Khan <skhan@linuxfoundation.org> wrote:
>
>>> 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?
>
> Yes please, it's mostly a lib/ thing.
Done.
Here is the link:
https://lore.kernel.org/all/20240924032200.167622-1-luis.hernandez093@gmail.com/
>
> I can't actually find the original patch email. f099bda563dd doesn't
> have a Link: to the submission (please update your scripts to fix
> this) and the patch wasn't cc'ed to anything to which I subscribe
> (please prefer to cc linux-kernel on most patches because of this).
>
Will do - thanks for the reminder.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-10-09 21:04 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
2024-10-09 20:42 ` Andrew Morton
2024-10-09 21:04 ` Shuah Khan [this message]
-- 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=25172760-bb70-4343-b79f-8cd5f082122c@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