linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Myron Stowe <myron.stowe@gmail.com>
Cc: linux-pci <linux-pci@vger.kernel.org>
Subject: Re: 2013 Linux Plumbers ACPI/PM, PCI Microconference proposal call for participaton
Date: Mon, 22 Apr 2013 14:24:47 -0600	[thread overview]
Message-ID: <1366662287.2918.459.camel@bling.home> (raw)
In-Reply-To: <CAL-B5D3mP-Eo7yzZb=ZJ_+GK5YGzKZV2p0SD05s3fXDR2BGorA@mail.gmail.com>

On Thu, 2013-04-18 at 15:52 -0600, Myron Stowe wrote:
> All:
> 
> We would like to hold a combined ACPI/PM, PCI focused microconference
> as part of this year's Linux Plumbers conference but first we need to
> show that there is enough interest and material that needs covered.
> 
> 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 (respond to this mail on the
> linux-pci list for tracking purposes please).  You should also feel
> free to submit ideas as proposals that others could cover.  This is
> the "Plumbers" conference so topics concerning userspace interaction
> with the kernel and not just topics concerning pure kernel subsystem
> internals would be greatly welcomed.

A few PCI discussion topics:

PCI secondary bus resets - How to avoid surprise hotplugs and/or how to
re-architect the device reset interface.

pci_is_pcie() - Not just for PCIe capabilities?  How to handle
non-compliant PCIe devices that don't expose a capability.

I/O port pci-sysfs resource files - Fix or remove?

Thanks,
Alex


      reply	other threads:[~2013-04-22 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 21:52 2013 Linux Plumbers ACPI/PM, PCI Microconference proposal call for participaton Myron Stowe
2013-04-22 20:24 ` Alex Williamson [this message]

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=1366662287.2918.459.camel@bling.home \
    --to=alex.williamson@redhat.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=myron.stowe@gmail.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 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).