On Mon, 2013-02-25 at 13:51 +0900, Yasuaki Ishimatsu wrote:
> Hi Toshi,
>
> 2013/02/23 4:42, Toshi Kani wrote:
> > In order to eject a memory device object represented as "PNP0C80:%d"
> > in sysfs, its associated memblocks (system/memory/memory%d) need to
> > be off-lined. However, there is no
On Mon, 2013-02-25 at 13:51 +0900, Yasuaki Ishimatsu wrote:
Hi Toshi,
2013/02/23 4:42, Toshi Kani wrote:
In order to eject a memory device object represented as PNP0C80:%d
in sysfs, its associated memblocks (system/memory/memory%d) need to
be off-lined. However, there is no user
Hi Toshi,
2013/02/23 4:42, Toshi Kani wrote:
> In order to eject a memory device object represented as "PNP0C80:%d"
> in sysfs, its associated memblocks (system/memory/memory%d) need to
> be off-lined. However, there is no user friendly way to correlate
> between a memory device object and its
Hi Toshi,
2013/02/23 4:42, Toshi Kani wrote:
In order to eject a memory device object represented as PNP0C80:%d
in sysfs, its associated memblocks (system/memory/memory%d) need to
be off-lined. However, there is no user friendly way to correlate
between a memory device object and its
In order to eject a memory device object represented as "PNP0C80:%d"
in sysfs, its associated memblocks (system/memory/memory%d) need to
be off-lined. However, there is no user friendly way to correlate
between a memory device object and its memblocks in sysfs.
This patch creates sysfs links to
In order to eject a memory device object represented as PNP0C80:%d
in sysfs, its associated memblocks (system/memory/memory%d) need to
be off-lined. However, there is no user friendly way to correlate
between a memory device object and its memblocks in sysfs.
This patch creates sysfs links to
6 matches
Mail list logo
