On Mon, 8 Apr 2013, Toshi Kani wrote:
> > So we don't need this new code if CONFIG_MEMORY_HOTPLUG=n? If so, can
> > we please arrange for it to not be present if the user doesn't need it?
>
> Good point! Yes, since the new function is intended for memory
> hot-delete and is only called from __r
On Mon, 2013-04-08 at 13:44 -0700, Andrew Morton wrote:
> On Mon, 8 Apr 2013 11:09:53 -0600 Toshi Kani wrote:
>
> > Memory hot-delete to a memory range present at boot causes an
> > error message in __release_region(), such as:
> >
> > Trying to free nonexistent resource <7000-
On Mon, 8 Apr 2013 11:09:53 -0600 Toshi Kani wrote:
> Memory hot-delete to a memory range present at boot causes an
> error message in __release_region(), such as:
>
> Trying to free nonexistent resource <7000-77ff>
>
> Hot-delete operation still continues since __rele
Memory hot-delete to a memory range present at boot causes an
error message in __release_region(), such as:
Trying to free nonexistent resource <7000-77ff>
Hot-delete operation still continues since __release_region() is
a void function, but the target memory range is no
4 matches
Mail list logo
