From: Don Dutile <ddutile@redhat.com>
To: "'astone@redhat.com'" <'astone@redhat.com'>,
Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Robert Richter <rrichter@cavium.com>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
Arnd Bergmann <arnd@arndb.de>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Jon Masters <jcm@redhat.com>,
linaro-acpi@lists.linaro.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Christopher Covington <cov@codeaurora.org>,
Sinan Kaya <okaya@codeaurora.org>,
Tomasz Nowicki <tn@semihalf.com>
Subject: Re: [Linaro-acpi] ACPI namespace details for ARM64
Date: Thu, 10 Nov 2016 22:33:34 -0500 [thread overview]
Message-ID: <58253C0E.4060003@redhat.com> (raw)
In-Reply-To: <a0829be4-6324-758b-2fe6-a274f715a3a9@linaro.org>
On 11/10/2016 06:18 PM, Al Stone wrote:
> On 11/09/2016 03:05 PM, Bjorn Helgaas wrote:
>> Hi all,
>>
>> We've been working through the details of getting ACPI to work on
>> arm64, and there have been lots of questions about what this means for
>> PCI. I've outlined this for several people individually, but I'm
>> going to send this separately, apart from a specific patch series, to
>> make sure we're all on the same page. Please correct my errors and
>> misunderstandings.
>>
>> Bjorn
>>
>> [snip....]
>
> A big +1 to all of this. This also looks like something that should
> be added to either PCI, ACPI or arm64 documentation (or even all three).
> What do you think?
>
> Thank you for putting this together, Bjorn.
>
>
+1. One-stop shopping! :)
Nice summary, and clarification(s).
next prev parent reply other threads:[~2016-11-11 3:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 22:05 ACPI namespace details for ARM64 Bjorn Helgaas
2016-11-09 22:05 ` Bjorn Helgaas
2016-11-10 23:18 ` [Linaro-acpi] " Al Stone
2016-11-10 23:18 ` Al Stone
2016-11-11 3:33 ` Don Dutile [this message]
2016-11-11 9:32 ` Lorenzo Pieralisi
2016-11-11 9:32 ` Lorenzo Pieralisi
2016-11-11 14:44 ` Hanjun Guo
2016-11-11 14:44 ` Hanjun Guo
2016-11-11 14:24 ` Sinan Kaya
2016-11-11 14:24 ` Sinan Kaya
2016-12-02 5:13 ` Jon Masters
2016-12-02 5:13 ` Jon Masters
2016-11-11 11:28 ` Lorenzo Pieralisi
2016-11-11 11:28 ` Lorenzo Pieralisi
2016-12-02 4:52 ` Jon Masters
2016-12-02 4:52 ` Jon Masters
2016-12-02 16:21 ` Bjorn Helgaas
2016-12-02 16:21 ` 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=58253C0E.4060003@redhat.com \
--to=ddutile@redhat.com \
--cc='astone@redhat.com' \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=cov@codeaurora.org \
--cc=gabriele.paoloni@huawei.com \
--cc=helgaas@kernel.org \
--cc=jcm@redhat.com \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rrichter@cavium.com \
--cc=tn@semihalf.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 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.