From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>,
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>,
Daniel Silsby <dansilsby@gmail.com>,
Paul Burton <paul.burton@mips.com>,
Paul Cercueil <paul@crapouillou.net>
Subject: linux-next: manual merge of the mips tree with the kbuild tree
Date: Mon, 26 Aug 2019 09:17:58 +1000 [thread overview]
Message-ID: <20190826091758.1a40ac66@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
Hi all,
Today's linux-next merge of the mips tree got a conflict in:
arch/mips/Kconfig
between commit:
2ff2b7ec65dc ("kbuild: add CONFIG_ASM_MODVERSIONS")
from the kbuild tree and commit:
45e03e62724f ("MIPS: Decouple CPU_SUPPORTS_HUGEPAGES from 64BIT")
from the mips 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.
--
Cheers,
Stephen Rothwell
diff --cc arch/mips/Kconfig
index 3db919b5c93a,31c7044e34e6..000000000000
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@@ -43,8 -44,7 +44,8 @@@ config MIP
select HAVE_ARCH_MMAP_RND_COMPAT_BITS if MMU && COMPAT
select HAVE_ARCH_SECCOMP_FILTER
select HAVE_ARCH_TRACEHOOK
- select HAVE_ARCH_TRANSPARENT_HUGEPAGE if CPU_SUPPORTS_HUGEPAGES && 64BIT
+ select HAVE_ARCH_TRANSPARENT_HUGEPAGE if CPU_SUPPORTS_HUGEPAGES
+ select HAVE_ASM_MODVERSIONS
select HAVE_EBPF_JIT if (!CPU_MICROMIPS)
select HAVE_CONTEXT_TRACKING
select HAVE_COPY_THREAD_TLS
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-08-25 23:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 23:17 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-25 23:17 linux-next: manual merge of the mips tree with the kbuild tree Stephen Rothwell
2018-08-02 23:21 Stephen Rothwell
2018-08-03 6:41 ` Christoph Hellwig
2018-08-03 6:42 ` Stephen Rothwell
2018-08-03 7:12 ` Christoph Hellwig
2018-08-03 7:51 ` Stephen Rothwell
2018-08-14 23:31 ` 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=20190826091758.1a40ac66@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dansilsby@gmail.com \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=paul@crapouillou.net \
--cc=ralf@linux-mips.org \
--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