From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Julian Vetter <jvetter@kalrayinc.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>
Subject: Re: linux-next: manual merge of the asm-generic tree with the mm tree
Date: Fri, 22 Nov 2024 10:56:11 +1100 [thread overview]
Message-ID: <20241122105611.38d8607e@canb.auug.org.au> (raw)
In-Reply-To: <20241029095525.0fba9d23@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]
Hi all,
On Tue, 29 Oct 2024 09:55:25 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the asm-generic tree got a conflict in:
>
> lib/Makefile
>
> between commit:
>
> 2ff14c29323d ("lib/Makefile: make union-find compilation conditional on CONFIG_CPUSETS")
>
> from the mm tree and commit:
>
> b660d0a2acb9 ("New implementation for IO memcpy and IO memset")
>
> from the asm-generic 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 lib/Makefile
> index 1eb89962daef,db4717538fad..000000000000
> --- a/lib/Makefile
> +++ b/lib/Makefile
> @@@ -35,12 -35,10 +35,12 @@@ lib-y := ctype.o string.o vsprintf.o cm
> is_single_threaded.o plist.o decompress.o kobject_uevent.o \
> earlycpio.o seq_buf.o siphash.o dec_and_lock.o \
> nmi_backtrace.o win_minmax.o memcat_p.o \
> - buildid.o objpool.o
> - buildid.o objpool.o union_find.o iomem_copy.o
> ++ buildid.o objpool.o iomem_copy.o
>
> +lib-$(CONFIG_UNION_FIND) += union_find.o
> lib-$(CONFIG_PRINTK) += dump_stack.o
> lib-$(CONFIG_SMP) += cpumask.o
> +lib-$(CONFIG_MIN_HEAP) += min_heap.o
>
> lib-y += kobject.o klist.o
> obj-y += lockref.o
This is now a conflict between the mm-non-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-11-21 23:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 22:55 linux-next: manual merge of the asm-generic tree with the mm tree Stephen Rothwell
2024-11-21 23:56 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-04 22:05 Stephen Rothwell
2024-01-10 22:22 ` Stephen Rothwell
2023-09-18 0:10 Stephen Rothwell
2023-09-18 1:28 ` Baoquan He
2023-11-02 21:34 ` 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=20241122105611.38d8607e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=jvetter@kalrayinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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