From mboxrd@z Thu Jan 1 00:00:00 1970 From: Toshi Kani Subject: Re: [PATCH v2] ACPI: Add sysfs links from memory device to memblocks Date: Tue, 26 Feb 2013 10:16:44 -0700 Message-ID: <1361899004.12845.96.camel@misato.fc.hp.com> References: <1361826130-31062-1-git-send-email-toshi.kani@hp.com> <512C4A07.40903@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from g6t0185.atlanta.hp.com ([15.193.32.62]:8449 "EHLO g6t0185.atlanta.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751223Ab3BZR1j (ORCPT ); Tue, 26 Feb 2013 12:27:39 -0500 In-Reply-To: <512C4A07.40903@jp.fujitsu.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Yasuaki Ishimatsu Cc: "rjw@sisk.pl" , "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "vasilis.liaskovitis@profitbricks.com" On Tue, 2013-02-26 at 05:37 +0000, Yasuaki Ishimatsu wrote: > 2013/02/26 6:02, 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 memblocks in sysfs. > > > > This patch creates sysfs links to memblocks under a memory device > > object so that a user can easily checks and manipulates its memblocks > > in sysfs. > > > > For example, when PNP0C80:05 is associated with memory8 and memory9, > > the following two links are created under PNP0C80:05. This allows > > a user to access memory8/9 directly from PNP0C80:05. > > > > # ll /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C80:05 > > lrwxrwxrwx. memory8 -> ../../../system/memory/memory8 > > lrwxrwxrwx. memory9 -> ../../../system/memory/memory9 > > > > Signed-off-by: Toshi Kani > > --- > > I confirmed that the patch has no problem. > Feel free to add: > > Tested-by: Yasuaki Ishimatsu > Acked-by: Yasuaki Ishimatsu Great! Thanks Yasuaki! -Toshi