From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jiri Kosina <jikos@kernel•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Michael Ellerman <mpe@ellerman•id.au>,
Li Zhang <zhlcindy@linux•vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation•org>
Subject: linux-next: manual merge of the livepatching tree with Linus' tree
Date: Mon, 18 Apr 2016 14:23:23 +1000 [thread overview]
Message-ID: <20160418142323.26fa9ae1@canb.auug.org.au> (raw)
Hi Jiri,
Today's linux-next merge of the livepatching tree got a conflict in:
arch/powerpc/Kconfig
between commit:
7f2bd0063342 ("powerpc/mm: enable page parallel initialisation")
from Linus' tree and commit:
85baa095497f ("powerpc/livepatch: Add live patching support on ppc64le")
from the livepatching 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.
Maybe the selects under config PPC should be sorted ...
--
Cheers,
Stephen Rothwell
diff --cc arch/powerpc/Kconfig
index fbebde0771c8,944a79a2768f..000000000000
--- a/arch/powerpc/Kconfig
+++ b/arch/powerpc/Kconfig
@@@ -159,7 -159,7 +159,8 @@@ config PP
select ARCH_HAS_DEVMEM_IS_ALLOWED
select HAVE_ARCH_SECCOMP_FILTER
select ARCH_HAS_UBSAN_SANITIZE_ALL
+ select ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT
+ select HAVE_LIVEPATCH if HAVE_DYNAMIC_FTRACE_WITH_REGS
config GENERIC_CSUM
def_bool CPU_LITTLE_ENDIAN
next reply other threads:[~2016-04-18 4:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 4:23 Stephen Rothwell [this message]
2016-04-19 1:57 ` linux-next: manual merge of the livepatching tree with Linus' tree Michael Ellerman
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=20160418142323.26fa9ae1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=jikos@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=zhlcindy@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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