From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Theodore Ts'o <tytso@mit.edu>, "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Donet Tom <donettom@linux.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Subject: Re: linux-next: manual merge of the random tree with the mm-stable tree
Date: Wed, 24 Jul 2024 09:16:59 +1000 [thread overview]
Message-ID: <20240724091659.27326953@canb.auug.org.au> (raw)
In-Reply-To: <20240709174340.5c03c2b9@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
Hi all,
On Tue, 9 Jul 2024 17:43:40 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the random tree got a conflict in:
>
> tools/testing/selftests/mm/Makefile
>
> between commit:
>
> 3a103b5315b7 ("selftest: mm: Test if hugepage does not get leaked during __bio_release_pages()")
>
> from the mm-stable tree and commit:
>
> 94beef29e110 ("mm: add MAP_DROPPABLE for designating always lazily freeable mappings")
>
> from the random 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.
>
> diff --cc tools/testing/selftests/mm/Makefile
> index e1aa09ddaa3d,e3e5740e13e1..000000000000
> --- a/tools/testing/selftests/mm/Makefile
> +++ b/tools/testing/selftests/mm/Makefile
> @@@ -75,7 -73,7 +75,8 @@@ TEST_GEN_FILES += ksm_functional_test
> TEST_GEN_FILES += mdwe_test
> TEST_GEN_FILES += hugetlb_fault_after_madv
> TEST_GEN_FILES += hugetlb_madv_vs_map
> +TEST_GEN_FILES += hugetlb_dio
> + TEST_GEN_FILES += droppable
>
> ifneq ($(ARCH),arm64)
> TEST_GEN_FILES += soft-dirty
This is now a conflict between the random tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-07-23 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 7:43 linux-next: manual merge of the random tree with the mm-stable tree Stephen Rothwell
2024-07-23 23:16 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-09 7:40 Stephen Rothwell
2024-07-23 23:15 ` Stephen Rothwell
2024-07-24 1:34 ` Jason A. Donenfeld
2024-07-02 6:40 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=20240724091659.27326953@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=donettom@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
/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