From: Bjorn Helgaas <bhelgaas@google.com>
To: Myron Stowe <myron.stowe@gmail.com>
Cc: linux-pci <linux-pci@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
"open list:INTEL IOMMU (VT-d)" <iommu@lists.linux-foundation.org>,
virtualization@lists.linux-foundation.org,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux Plumbers ACPI/PM, PCI Microconference
Date: Tue, 23 Jul 2013 10:06:26 -0600 [thread overview]
Message-ID: <CAErSpo7TexM5-7Z=8H+B5=49-GzoKd_prn=LbMFZWV9rpdn__A@mail.gmail.com> (raw)
In-Reply-To: <CAL-B5D03ki8NHsM6EuESTH2K-Eh+XyFHNXPDYwgDq+oagDjtMQ@mail.gmail.com>
On Tue, Jul 16, 2013 at 8:21 PM, Myron Stowe <myron.stowe@gmail.com> wrote:
> Linux Plumbers has approved an ACPI/PM, PCI microconference. The
> overview page is here:
>
> http://wiki.linuxplumbersconf.org/2013:pci_subsystem
>
> We would like to start receiving volunteers for presenting topics of
> interest. There is a lot of activity in these subsystems so please
> respond by submitting presentation or discussion proposals that you
> would be willing to cover for consideration. You should also feel
> free to submit ideas as proposals that others could cover.
Somebody else privately suggested these ARM/PCI topics:
> -> how it's been cleaned up to be more common across arm-32 machines
> -> dependencies on dtb
> -> future use/dependency(s) on ACPI
> -> hotplug support issues (if any; acpi (host-bridge) vs <whatever ARM uses> ?)
and I'm interested in those as well. There seems to be a lot of
activity in that area. In addition, I'm interested in ARM IOMMU
support. I see drivers/iommu/arm-smmu.c, but it's brand-new and I
haven't looked at it at all.
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: bhelgaas@google.com (Bjorn Helgaas)
To: linux-arm-kernel@lists.infradead.org
Subject: Linux Plumbers ACPI/PM, PCI Microconference
Date: Tue, 23 Jul 2013 10:06:26 -0600 [thread overview]
Message-ID: <CAErSpo7TexM5-7Z=8H+B5=49-GzoKd_prn=LbMFZWV9rpdn__A@mail.gmail.com> (raw)
In-Reply-To: <CAL-B5D03ki8NHsM6EuESTH2K-Eh+XyFHNXPDYwgDq+oagDjtMQ@mail.gmail.com>
On Tue, Jul 16, 2013 at 8:21 PM, Myron Stowe <myron.stowe@gmail.com> wrote:
> Linux Plumbers has approved an ACPI/PM, PCI microconference. The
> overview page is here:
>
> http://wiki.linuxplumbersconf.org/2013:pci_subsystem
>
> We would like to start receiving volunteers for presenting topics of
> interest. There is a lot of activity in these subsystems so please
> respond by submitting presentation or discussion proposals that you
> would be willing to cover for consideration. You should also feel
> free to submit ideas as proposals that others could cover.
Somebody else privately suggested these ARM/PCI topics:
> -> how it's been cleaned up to be more common across arm-32 machines
> -> dependencies on dtb
> -> future use/dependency(s) on ACPI
> -> hotplug support issues (if any; acpi (host-bridge) vs <whatever ARM uses> ?)
and I'm interested in those as well. There seems to be a lot of
activity in that area. In addition, I'm interested in ARM IOMMU
support. I see drivers/iommu/arm-smmu.c, but it's brand-new and I
haven't looked at it at all.
Bjorn
next prev parent reply other threads:[~2013-07-23 16:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 2:21 Linux Plumbers ACPI/PM, PCI Microconference Myron Stowe
2013-07-17 2:21 ` Myron Stowe
2013-07-17 14:31 ` Shuah Khan
2013-07-17 14:31 ` Shuah Khan
2013-07-17 14:31 ` Shuah Khan
2013-07-30 23:48 ` Rafael J. Wysocki
2013-07-30 23:48 ` Rafael J. Wysocki
2013-07-30 23:48 ` Rafael J. Wysocki
2013-07-31 0:02 ` Shuah Khan
2013-07-31 0:02 ` Shuah Khan
2013-07-31 0:02 ` Shuah Khan
2013-07-31 0:02 ` Shuah Khan
2013-07-31 0:36 ` Alex Williamson
2013-07-31 0:36 ` Alex Williamson
2013-07-31 0:36 ` Alex Williamson
2013-07-31 0:36 ` Alex Williamson
2013-07-31 0:36 ` Alex Williamson
2013-07-23 16:06 ` Bjorn Helgaas [this message]
2013-07-23 16:06 ` Bjorn Helgaas
2013-07-24 16:30 ` Shuah Khan
[not found] ` <CAErSpo7TexM5-7Z=8H+B5=49-GzoKd_prn=LbMFZWV9rpdn__A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-24 16:30 ` Shuah Khan
2013-07-24 16:30 ` Shuah Khan
2013-07-24 16:30 ` Shuah Khan
2013-07-24 16:30 ` Shuah Khan
2013-07-31 11:40 ` [Announcement] " Rafael J. Wysocki
[not found] ` <CAL-B5D03ki8NHsM6EuESTH2K-Eh+XyFHNXPDYwgDq+oagDjtMQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-31 11:40 ` Rafael J. Wysocki
2013-07-31 11:40 ` Rafael J. Wysocki
[not found] ` <1755363.sGc8nLIQOW-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2013-07-31 16:35 ` Shuah Khan
2013-07-31 16:35 ` Shuah Khan
2013-07-31 16:35 ` Shuah Khan
2013-07-31 21:17 ` Rafael J. Wysocki
2013-07-31 21:17 ` Rafael J. Wysocki
2013-07-31 21:17 ` Rafael J. Wysocki
2013-08-01 19:45 ` Shuah Khan
2013-08-01 19:45 ` Shuah Khan
2013-08-01 19:45 ` Shuah Khan
2013-08-01 19:45 ` Shuah Khan
2013-07-31 16:35 ` Shuah Khan
2013-08-09 18:12 Myron Stowe
2013-08-09 18:12 ` Myron Stowe
2013-08-09 18:12 ` Myron Stowe
2013-08-09 21:37 ` Rafael J. Wysocki
2013-08-09 21:37 ` Rafael J. Wysocki
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='CAErSpo7TexM5-7Z=8H+B5=49-GzoKd_prn=LbMFZWV9rpdn__A@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=myron.stowe@gmail.com \
--cc=virtualization@lists.linux-foundation.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.