From: Tang Chen <tangchen@cn.fujitsu.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: jiang.liu@huawei.com, bhelgaas@google.com, lenb@kernel.org,
izumi.taku@jp.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Update acpi_root_bridge_list in container hotplug path.
Date: Wed, 17 Oct 2012 15:39:46 +0800 [thread overview]
Message-ID: <507E60C2.6010104@cn.fujitsu.com> (raw)
In-Reply-To: <CAE9FiQVFc9VVfWZpEfjPeGvo5pby3BQNzDei3VTXdoR048_SPg@mail.gmail.com>
On 10/17/2012 01:18 PM, Yinghai Lu wrote:
>
> no, we don't need that.
>
> after closely looking, it seems we can dump acpi_root_bridge.
>
> please check if attached patch could work with container path.
Hi Yinghai,
Your patch seems working well.
BTW, I actually found that the two lists, acpi_root_bridge and
acpi_pci_roots in drivers/acpi/pci_root.c were similar, except
your acpi_root_bridge included PNP0A08.
In the beginning, I thought you would use it in some other situations,
and now it is clear that it can be removed.
Thanks. :)
And also, I have another 2 questions, maybe you can help me.
1) Do we need to put PNP0A08 into acpi_pci_roots ?
2) In container_notify_cb(), when it got a ACPI_NOTIFY_EJECT_REQUEST
event, it doesn't do the hot-remove things.
I use your sci emulator patch to test it. I did the following thing:
echo echo "\_SB_.LSB1" > /sys/kernel/debug/acpi/sci_notify
where \_SB_.LSB1 is a container, it just did nothing.
Do we need to support this operation ?
Thanks. :)
>
> Thanks
>
> Yinghai
next prev parent reply other threads:[~2012-10-17 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 3:25 [PATCH 1/1] Update acpi_root_bridge_list in container hotplug path Tang Chen
2012-10-17 5:18 ` Yinghai Lu
2012-10-17 7:39 ` Tang Chen [this message]
2012-10-17 7:42 ` Tang Chen
2012-10-17 16:28 ` Yinghai Lu
2012-10-18 1:00 ` Tang Chen
2012-10-19 8:49 ` Tang Chen
2012-10-19 20:36 ` Yinghai Lu
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=507E60C2.6010104@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=bhelgaas@google.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=jiang.liu@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.