From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Brian Norris <computersforpeace@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: linux-next: manual merge of the l2-mtd tree with the kbuild-current tree
Date: Tue, 22 Aug 2017 07:37:01 +0200 [thread overview]
Message-ID: <20170822073701.34d77cc8@bbrezillon> (raw)
In-Reply-To: <20170822115614.1590b368@canb.auug.org.au>
Le Tue, 22 Aug 2017 11:56:14 +1000,
Stephen Rothwell <sfr@canb.auug.org.au> a écrit :
> Hi Brian,
>
> Today's linux-next merge of the l2-mtd tree got a conflict in:
>
> include/asm-generic/vmlinux.lds.h
>
> between commit:
>
> cb87481ee89d ("kbuild: linker script do not match C names unless LD_DEAD_CODE_DATA_ELIMINATION is configured")
Masahiro, according to this message [1], you queued the above patch to
your fixes branch. Do you plan to send a fixes PR to Linus before
-rc7? If that's the case I'll merge -rc7 in l2-mtd/master, otherwise
I'll need an immutable branch.
Thanks,
Boris
[1]https://www.spinics.net/lists/arm-kernel/msg599088.html
>
> from the kbuild-current tree and commit:
>
> 129f6c4820dd ("mtd: only use __xipram annotation when XIP_KERNEL is set")
>
> from the l2-mtd 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.
>
next prev parent reply other threads:[~2017-08-22 5:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 1:56 linux-next: manual merge of the l2-mtd tree with the kbuild-current tree Stephen Rothwell
2017-08-22 5:37 ` Boris Brezillon [this message]
2017-08-22 5:44 ` Masahiro Yamada
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=20170822073701.34d77cc8@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=arnd@arndb.de \
--cc=computersforpeace@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=yamada.masahiro@socionext.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