From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Borislav Petkov <bp@alien8•de>,
Palmer Dabbelt <palmer@dabbelt•com>,
Paul Walmsley <paul@pwsan•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Yash Shah <yash.shah@sifive•com>, Alexandre Ghiti <alex@ghiti•fr>
Subject: linux-next: manual merge of the edac-amd tree with the risc-v tree
Date: Mon, 8 Jul 2019 17:01:34 +1000 [thread overview]
Message-ID: <20190708170134.15f225ca@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
Hi all,
Today's linux-next merge of the edac-amd tree got a conflict in:
arch/riscv/Kconfig
between commit:
9e953cda5cdf ("riscv: Introduce huge page support for 32/64bit kernel")
from the risc-v tree and commit:
a1ee570c831d ("EDAC/sifive: Add EDAC platform driver for SiFive SoCs")
from the edac-amd 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/riscv/Kconfig
index 8bf447b36955,4961deaa3b1d..000000000000
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@@ -51,8 -50,7 +51,9 @@@ config RISC
select ARCH_HAS_PTE_SPECIAL
select ARCH_HAS_MMIOWB
select HAVE_EBPF_JIT if 64BIT
+ select ARCH_HAS_GIGANTIC_PAGE
+ select ARCH_WANT_HUGE_PMD_SHARE if 64BIT
+ select EDAC_SUPPORT
config MMU
def_bool y
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2019-07-08 7:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190708170134.15f225ca@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alex@ghiti$(echo .)fr \
--cc=bp@alien8$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=palmer@dabbelt$(echo .)com \
--cc=paul@pwsan$(echo .)com \
--cc=yash.shah@sifive$(echo .)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