Re: [3/3] sparsemem memory model for ppc64

Olof Johansson wrote:
> Hi,
> 
> Just two formatting nitpicks below.

Thanks, this would be better served by rewriting the first comment and
removing the second all together.

/* Add all physical memory to the bootmem map, mark each area
 * present.  The first block has already been marked present above.
 */

I note that the diff in question has sneaked into the wrong patch, that
segement represents memory_present.  So I'll rediff them with it there.
 No overall change to the code.

-apw
-
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:
  • sparsemem ppc64 tidy flat memory comments and fix benign mempresent call
    • From: Andy Whitcroft <[email protected]>

• References:
  • [3/3] sparsemem memory model for ppc64
    • From: Andy Whitcroft <[email protected]>
  • Re: [3/3] sparsemem memory model for ppc64
    • From: Olof Johansson <[email protected]>

• Prev by Date: Re: Bug: 2.6.11.8 msdos.c
• Next by Date: Re: Bug: 2.6.11.8 msdos.c
• Previous by thread: Re: [3/3] sparsemem memory model for ppc64
• Next by thread: sparsemem ppc64 tidy flat memory comments and fix benign mempresent call
• 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]