From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: linux-pci@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
David Woodhouse <dwmw2@infradead.org>,
Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh@kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Will Deacon <will.deacon@arm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Keith Busch <keith.busch@intel.com>,
Joerg Roedel <joro@8bytes.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Alex Williamson <alex.williamson@redhat.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Myron Stowe <myron.stowe@gmail.com>,
Auger Eric <eric.auger@redhat.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: LPC16 PCI microconference - Call for sessions proposals
Date: Mon, 13 Jun 2016 18:18:23 +0100 [thread overview]
Message-ID: <20160613171823.GA29621@red-moon> (raw)
Hi,
following the official LPC16 PCI uconf acceptance notification:
https://www.linuxplumbersconf.org/2016/pci-microconference-accepted-into-2016-linux-plumbers-conference/
I am sending out a call for sessions proposals open to all developers
interested/involved in Linux kernel PCI development.
The LPC16 uconf wiki provides a list of topics that we put forward for
the microconference submission:
http://wiki.linuxplumbersconf.org/2016:pci
The wiki is there to provide a list of topics that we considered key
and it should not be considered final, actually it is a starting point
to define a possible schedule structure.
Session proposals for the LPC16 PCI microconference are warmly encouraged
and can be submitted here:
http://www.linuxplumbersconf.org/2016/ocw/events/LPC2016/tracks/531
Maintainers in CC, as an initial step we singled out the main subtracks
below and I would be grateful if you could add a session through the link
above and run the respective session (in brackets people whom I know are
involved in the topic and are likely to be asked to run/take part in the
session; NB: it is obviously incomplete, and it is based on what we
could infer from current PCI related patches, please do manifest your
interest):
- PCI resources allocation/validation/cross-arch consolidation
([Bjorn, Lorenzo, Yinghai, Benjamin, Jesse, Arnd])
- PCI Virtualization (cross-topic)
([Alex, Bjorn, Eric, Marc, Joerg, Will, David])
- PCI MSI ([Alex, Eric, Marc])
- PCI IOMMU ([Joerg, David, Jesse, Will, Marc])
- PCIe (ATS, PRI) ([Jesse, Will])
- PCIe root ports power management ([Rafael])
- PCI DT/ACPI - consolidation ([Bjorn, Lorenzo, Arnd, Rob])
Anyone involved in PCI kernel development, if you wish to add sessions and
attend the microconference consider yourself welcome, for any questions
just reply to this thread or drop me a line.
Looking forward to meeting you all in Santa Fe for this interesting track !
Lorenzo
next reply other threads:[~2016-06-13 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 17:18 Lorenzo Pieralisi [this message]
2016-09-15 8:38 ` LPC16 PCI microconference - Call for sessions proposals Kishon Vijay Abraham I
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=20160613171823.GA29621@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=alex.williamson@redhat.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=dwmw2@infradead.org \
--cc=eric.auger@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=joro@8bytes.org \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=myron.stowe@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=will.deacon@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).