From: Mark Brown <broonie@kernel•org>
To: Andrew Morton <akpm@linux-foundation•org>,
Mike Rapoport <rppt@linux•ibm.com>,
Greentime Hu <greentime.hu@sifive•com>,
Paul Walmsley <paul.walmsley@sifive•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: manual merge of the akpm-current tree with the risc-v-fixes tree
Date: Fri, 20 Sep 2019 16:35:35 +0100 [thread overview]
Message-ID: <20190920153535.GG3822@sirena.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/riscv/include/asm/pgtable.h
between commit:
b6f2b2e600a27b798 ("RISC-V: Fix building error when CONFIG_SPARSEMEM_MANUAL=y")
from the risc-v-fixes tree and commit:
e10b0ff68eee9f59 ("mm: consolidate pgtable_cache_init() and pgd_cache_init()")
from the akpm-current 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 arch/riscv/include/asm/pgtable.h
index 1be4f70ab2660,f45f6fbd2a50d..0000000000000
--- a/arch/riscv/include/asm/pgtable.h
+++ b/arch/riscv/include/asm/pgtable.h
@@@ -439,13 -411,12 +439,8 @@@ extern void *dtb_early_va
extern void setup_bootmem(void);
extern void paging_init(void);
- static inline void pgtable_cache_init(void)
- {
- /* No page table caches to initialize */
- }
-#define VMALLOC_SIZE (KERN_VIRT_SIZE >> 1)
-#define VMALLOC_END (PAGE_OFFSET - 1)
-#define VMALLOC_START (PAGE_OFFSET - VMALLOC_SIZE)
--
/*
- * Task size is 0x4000000000 for RV64 or 0xb800000 for RV32.
+ * Task size is 0x4000000000 for RV64 or 0x9fc00000 for RV32.
* Note that PGDIR_SIZE must evenly divide TASK_SIZE.
*/
#ifdef CONFIG_64BIT
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2019-09-20 15:35 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=20190920153535.GG3822@sirena.co.uk \
--to=broonie@kernel$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=greentime.hu@sifive$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.walmsley@sifive$(echo .)com \
--cc=rppt@linux$(echo .)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