public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Toshi Kani <toshi.kani@hp.com>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: "rjw@sisk.pl" <rjw@sisk.pl>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"vasilis.liaskovitis@profitbricks.com"
	<vasilis.liaskovitis@profitbricks.com>
Subject: Re: [PATCH v2] ACPI: Add sysfs links from memory device to memblocks
Date: Tue, 26 Feb 2013 10:16:44 -0700	[thread overview]
Message-ID: <1361899004.12845.96.camel@misato.fc.hp.com> (raw)
In-Reply-To: <512C4A07.40903@jp.fujitsu.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 <toshi.kani@hp.com>
> > ---
> 
> I confirmed that the patch has no problem.
> Feel free to add:
> 
> Tested-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
> Acked-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>

Great!  Thanks Yasuaki!
-Toshi



  reply	other threads:[~2013-02-26 17:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 21:02 [PATCH v2] ACPI: Add sysfs links from memory device to memblocks Toshi Kani
2013-02-26  5:37 ` Yasuaki Ishimatsu
2013-02-26 17:16   ` Toshi Kani [this message]
2013-03-26 13:04 ` Rafael J. Wysocki
2013-03-26 15:42   ` Toshi Kani
2013-03-26 22:39     ` Rafael J. Wysocki
2013-03-26 22:59       ` Toshi Kani
2013-03-26 23:39         ` Rafael J. Wysocki
2013-03-27 17:13           ` Toshi Kani
2013-04-11 22:23             ` Rafael J. Wysocki
2013-04-12 18:13               ` Toshi Kani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1361899004.12845.96.camel@misato.fc.hp.com \
    --to=toshi.kani@hp.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=vasilis.liaskovitis@profitbricks.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox