Re: [PATCH] catch valid mem range at onlining memory

Greg KH <[email protected]> wrote:
>
> > This all looks fairly (but trivially) dependent upon the 64-bit-resource
> > patches in Greg's tree.  Greg, were you planning on merging them in the
> > post-2.6.17 flood?
> 
> Yes, I was,

OK, thanks.

> unless there are any objections to me doing this?

I'd consider the patches as they stand to be ready to roll.

All the code bloat's a bit sad though.  It would have been nice to have
made the type of resource.start and .end Kconfigurable.  What happened
to that?

-
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] catch valid mem range at onlining memory
  - From: Greg KH <[email protected]>

References:
- [PATCH] catch valid mem range at onlining memory
  - From: KAMEZAWA Hiroyuki <[email protected]>
- Re: [PATCH] catch valid mem range at onlining memory
  - From: Andrew Morton <[email protected]>
- Re: [PATCH] catch valid mem range at onlining memory
  - From: Greg KH <[email protected]>

Prev by Date: Re: Linux I/O scheduling - ionice & co
Next by Date: Re: sata_sil24 resetting controller...
Previous by thread: Re: [PATCH] catch valid mem range at onlining memory
Next by thread: Re: [PATCH] catch valid mem range at onlining memory
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]