From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Luis Chamberlain <mcgrof@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Mike Rapoport (IBM)" <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>
Subject: Re: linux-next: manual merge of the modules tree with the mm tree
Date: Fri, 17 May 2024 09:26:07 +1000 [thread overview]
Message-ID: <20240517092607.0e3ec389@canb.auug.org.au> (raw)
In-Reply-To: <20240424122034.5b4a1a01@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
Hi all,
On Wed, 24 Apr 2024 12:20:34 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the modules tree got a conflict in:
>
> arch/powerpc/mm/mem.c
>
> between commit:
>
> c22e503ced5b ("fix missing vmalloc.h includes")
>
> from the mm-unstable branch of the mm tree and commit:
>
> 7aa7eb8269ea ("arch: make execmem setup available regardless of CONFIG_MODULES")
>
> from the modules 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 arch/powerpc/mm/mem.c
> index a197d4c2244b,5de62a3c1d4b..000000000000
> --- a/arch/powerpc/mm/mem.c
> +++ b/arch/powerpc/mm/mem.c
> @@@ -16,7 -16,7 +16,8 @@@
> #include <linux/highmem.h>
> #include <linux/suspend.h>
> #include <linux/dma-direct.h>
> +#include <linux/vmalloc.h>
> + #include <linux/execmem.h>
>
> #include <asm/swiotlb.h>
> #include <asm/machdep.h>
This is now a conflict between the mm-stable 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-05-16 23:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 2:20 linux-next: manual merge of the modules tree with the mm tree Stephen Rothwell
2024-05-16 23:26 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-24 2:39 Stephen Rothwell
2024-04-24 20:07 ` Andrew Morton
2024-04-24 20:17 ` Suren Baghdasaryan
2024-04-24 20:29 ` Mike Rapoport
2024-04-24 20:33 ` Suren Baghdasaryan
2024-04-24 21:24 ` Suren Baghdasaryan
2024-04-25 1:37 ` Stephen Rothwell
2024-04-12 2:04 Stephen Rothwell
2024-05-16 23:23 ` Stephen Rothwell
2024-05-16 23:35 ` 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=20240517092607.0e3ec389@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=rppt@kernel.org \
--cc=surenb@google.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