Re: [PATCH -mm -v4 1/3] i386/x86_64 boot: setup data

> Care to add a line of documentation if you keep it in mm/memory.c?

It would be better to just use early_ioremap() (or ioremap())

That is how ACPI who has similar issues accessing its tables solves this.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH -mm -v4 1/3] i386/x86_64 boot: setup data
    • From: "huang ying" <[email protected]>

• References:
  • [PATCH -mm -v4 1/3] i386/x86_64 boot: setup data
    • From: "Huang, Ying" <[email protected]>
  • Re: [PATCH -mm -v4 1/3] i386/x86_64 boot: setup data
    • From: Nick Piggin <[email protected]>

• Prev by Date: Re: [RFC/RFT] kbuild: save ARCH & CROSS_COMPILE
• Next by Date: Re: [RFC][PATCH] Escaping the arguments of kernel messages for sane user-space localisation
• Previous by thread: Re: [PATCH -mm -v4 1/3] i386/x86_64 boot: setup data
• Next by thread: Re: [PATCH -mm -v4 1/3] i386/x86_64 boot: setup data
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]