From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: linux-pci@vger.kernel.org, kvm@vger.kernel.org,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>
Cc: will.deacon@arm.com, marc.zyngier@arm.com,
jean-philippe.brucker@arm.com, bhelgaas@google.com,
joro@8bytes.org, alex.williamson@redhat.com, yinghai@kernel.org,
keith.busch@intel.com, benh@kernel.crashing.org,
jacob.jun.pan@linux.intel.com, yi.l.liu@intel.com,
alexander.deucher@amd.com, kevin.tian@intel.com,
ashok.raj@intel.com, okaya@codeaurora.org,
myron.stowe@redhat.com, leonro@mellanox.com, ddutile@redhat.com,
gabriele.paoloni@huawei.com
Subject: [CFP] VFIO/IOMMU/PCI microconference at LPC 2017
Date: Mon, 7 Aug 2017 19:01:08 +0100 [thread overview]
Message-ID: <20170807180108.GA28224@red-moon> (raw)
Hi,
following the official LPC17 VFIO/IOMMU/PCI uconf acceptance notification:
https://www.linuxplumbersconf.org/2017/vfioiommupci-microconference-accepted-into-linux-plumbers-conference/
I am sending out a call for sessions proposals open to all developers
interested/involved in Linux kernel VFIO/IOMMU/PCI development.
The LPC17 uconf wiki provides a list of topics that we put forward for
the microconference submission:
http://wiki.linuxplumbersconf.org/2017:vfio_iommu_pci
The wiki is there to provide a list of topics that we considered key
but it should not be considered final, actually it is a starting point
to define a possible schedule structure.
Session proposals for the LPC17 VFIO/IOMMU/PCI microconference are warmly
encouraged and can be submitted here:
https://linuxplumbersconf.org/2017/ocw/events/LPC2017/tracks/636
Anyone involved in VFIO/IOMMU/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 Los Angeles !
Lorenzo
reply other threads:[~2017-08-07 18:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170807180108.GA28224@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=alex.williamson@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=ashok.raj@intel.com \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=gabriele.paoloni@huawei.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jean-philippe.brucker@arm.com \
--cc=joro@8bytes.org \
--cc=keith.busch@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=myron.stowe@redhat.com \
--cc=okaya@codeaurora.org \
--cc=will.deacon@arm.com \
--cc=yi.l.liu@intel.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