Skip to contentSkip to conversation

ARM: nommu: Implement dummy early_paging_init()

PATCH New Thierry Reding 2 participants 4 messages Oct 23, 2013 – Nov 6, 2013 Arm (32-bit)

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ARM: nommu: Implement dummy early_paging_init()

No-MMU configurations currenty fail to build because they are missing the early_paging_init() symbol.

---
 arch/arm/mm/nommu.c | 9 +++++++++
 1 file changed, 9 insertions(+)
arch/arm/mm/nommu.c +9 -0
index 34d4ab2..5c668b7 100644
@@ -296,6 +296,15 @@ void __init sanity_check_meminfo(void)
 }
 
 /*
+ * early_paging_init() recreates boot time page table setup, allowing machines
+ * to switch over to a high (>4G) address space on LPAE systems
+ */
+void __init early_paging_init(const struct machine_desc *mdesc,
+			      struct proc_info_list *procinfo)
+{
+}
+
+/*
  * paging_init() sets up the page tables, initialises the zone memory
  * maps, and sets up the zero page, bad page and bad page tables.
  */
Signature · 1 line
1.8.4
#1 lore raw

PATCH 1/1 ARM: nommu: Implement dummy early_paging_init()

Quoted 4 lines · Thierry Reding

No-MMU configurations currenty fail to build because they are missing the early_paging_init() symbol.

This is still showing up on -next with at91x40_defconfig. Can you feed it to the patch tracker if you haven't already?

Thanks,

-Olof

#2 lore raw

PATCH 1/1 ARM: nommu: Implement dummy early_paging_init()

Quoted 11 lines · Olof Johansson
Quoted 4 lines · Thierry Reding

No-MMU configurations currenty fail to build because they are missing the early_paging_init() symbol.

This is still showing up on -next with at91x40_defconfig. Can you feed it to the patch tracker if you haven't already?

Done. I'm not sure exactly what the prerequisites are for submitting a patch to the tracker. The help text on the website says patches should be reviewed on the mailing list first and that's what I was waiting for. Is there some amount of time (a week or two) after which silence can be considered acknowledgement?

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131106/545a44f4/attachment.sig>

#3 lore raw

PATCH 1/1 ARM: nommu: Implement dummy early_paging_init()

Quoted 10 lines · Thierry Reding
Quoted 9 lines · Olof Johansson
Quoted 4 lines · Thierry Reding

No-MMU configurations currenty fail to build because they are missing the early_paging_init() symbol.

Quoted 8 lines
Quoted 2 lines

This is still showing up on -next with at91x40_defconfig. Can you feed it to the patch tracker if you haven't already?

Done. I'm not sure exactly what the prerequisites are for submitting a patch to the tracker. The help text on the website says patches should be reviewed on the mailing list first and that's what I was waiting for. Is there some amount of time (a week or two) after which silence can be considered acknowledgement?

Well, I just reviewed it for you (well, acked it :-). It's always hard to tell with a posted patch that hasn't received comments, but after a while it's usually ok to post to the tracker.

The LAKML volume is too high to see every patch and review it. I'm sure Russell will let you know if you get too trigger happy at sending to the tracker too. :-)

-Olof