From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Thomas Renninger <trenn@suse.de>,
kamezawa.hiroyu@jp.fujitsu.com, Len Brown <lenb@kernel.org>,
Tony Vroon <tony@linx.net>, Alex Chiang <achiang@hp.com>,
linux-acpi@vger.kernel.org,
Carlos Corbacho <carlos@strangeworlds.co.uk>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
Jonathan Woithe <jwoithe@physics.adelaide.edu.au>,
Zhao Yakui <yakui.zhao@intel.com>,
Mattia Dongili <malattia@linux.it>,
Harald Welte <laforge@gnumonks.org>,
Venki Pallipadi <venkatesh.pallipadi@intel.com>,
Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>,
Zhang Rui <rui.zhang@intel.com>, Matthew Garrett <mjg@redhat.com>
Subject: Re: [PATCH 01/10] ACPI: support acpi_device_ops .notify methods
Date: Sat, 04 Apr 2009 07:43:51 +0900 [thread overview]
Message-ID: <20090404074212.B9C4.E1E9C6FF@jp.fujitsu.com> (raw)
In-Reply-To: <200904030909.56982.bjorn.helgaas@hp.com>
> On Thursday 02 April 2009 06:23:16 pm Yasunori Goto wrote:
> > > On Thursday 02 April 2009 07:56:28 am Thomas Renninger wrote:
> > > > I remember these two guys helped me testing on memory hotplug.
> > > > They only had a simulator, but might want to give the latest kernel a try if
> > > > you come to clean up acpi_memhotplug.c:
> > > > kamezawa.hiroyu@jp.fujitsu.com
> > > > Yasunori Goto <y-goto@jp.fujitsu.com>
> >
> > I can use real machine which can memory hotplug.
> > In our case, notify method is called for container device (NUMA node),
> > and memory and processor devices are added under acpi_bus_scan().
> >
> > I'll book it to test this patch in next week.
> > It must be good test. :-)
>
> Thomas is right; I don't think it's worth your time to do much testing
> right now. These patches only affect device notifications, and I think
> the container/memory/processor stuff you're referring to depends on the
> system notifications. So this series should not affect the hotplug
> path.
Ah, OK. I misunderstood something.
Sorry for noise.
>
> I am working on some changes to the hotplug path, but that looks much
> more difficult, so it'll probably be a while before anything comes of
> it. Thanks for the tip; I'll make sure to CC: you when I post patches.
--
Yasunori Goto
next prev parent reply other threads:[~2009-04-03 22:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 17:48 [PATCH 00/10] ACPI: add device .notify methods Bjorn Helgaas
2009-03-30 17:48 ` [PATCH 01/10] ACPI: support acpi_device_ops " Bjorn Helgaas
2009-04-02 13:56 ` Thomas Renninger
2009-04-02 15:03 ` Bjorn Helgaas
2009-04-03 0:23 ` Yasunori Goto
2009-04-03 9:08 ` Thomas Renninger
2009-04-03 15:09 ` Bjorn Helgaas
2009-04-03 22:43 ` Yasunori Goto [this message]
2009-04-03 13:14 ` Thomas Renninger
2009-03-30 17:48 ` [PATCH 02/10] ACPI: button: use .notify method instead of installing handler directly Bjorn Helgaas
2009-03-30 17:48 ` [PATCH 03/10] ACPI: processor: " Bjorn Helgaas
2009-03-30 17:48 ` [PATCH 04/10] ACPI: thermal: " Bjorn Helgaas
2009-03-30 17:48 ` [PATCH 05/10] ACPI: video: " Bjorn Helgaas
2009-03-30 17:48 ` [PATCH 06/10] fujitsu-laptop: " Bjorn Helgaas
2009-03-31 6:45 ` [PATCH 06/10] fujitsu-laptop: use .notify method instead of Jonathan Woithe
2009-03-31 21:38 ` [PATCH 06/10] fujitsu-laptop: use .notify method instead of installing handler directly Tony Vroon
2009-03-31 22:09 ` Bjorn Helgaas
2009-03-31 22:09 ` Tony Vroon
2009-03-31 22:29 ` Jonathan Woithe
2009-03-30 17:48 ` [PATCH 07/10] fujitsu-laptop: use .notify method instead of installing hotkey " Bjorn Helgaas
2009-03-31 21:39 ` Tony Vroon
2009-03-31 22:30 ` [PATCH 07/10] fujitsu-laptop: use .notify method instead of installing " Jonathan Woithe
2009-03-30 17:48 ` [PATCH 08/10] panasonic-laptop: " Bjorn Helgaas
2009-03-30 17:48 ` [PATCH 09/10] sony-laptop: " Bjorn Helgaas
2009-03-31 13:46 ` Mattia Dongili
2009-03-31 22:58 ` Mattia Dongili
2009-03-30 17:48 ` [PATCH 10/10] ACPI: WMI: " Bjorn Helgaas
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=20090404074212.B9C4.E1E9C6FF@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=achiang@hp.com \
--cc=alexey.y.starikovskiy@linux.intel.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bjorn.helgaas@hp.com \
--cc=carlos@strangeworlds.co.uk \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=laforge@gnumonks.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=malattia@linux.it \
--cc=mjg@redhat.com \
--cc=rui.zhang@intel.com \
--cc=tony@linx.net \
--cc=trenn@suse.de \
--cc=venkatesh.pallipadi@intel.com \
--cc=yakui.zhao@intel.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