linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajat Jain <rajatjain.linux@gmail.com>
To: Linux-PCI <linux-pci@vger.kernel.org>
Subject: test mail 9
Date: Tue, 19 Nov 2013 14:54:35 -0800	[thread overview]
Message-ID: <528BEC2B.4040208@gmail.com> (raw)


Hello,

This patch set enables the use of PCI Express link up and link down events
for Hotplug or Unplug. The requirement of such a feature was originally
discussed here:

http://www.spinics.net/lists/linux-pci/msg05783.html
http://www.spinics.net/lists/hotplug/msg05801.html

Patch [1/4]: makes a function non-static for use by patch 2.
Patch [2/4]: Contains the bulk logic to allow link events to be used
             for hotplug and removal.
Patch [3/4]: Makes the pciehp_power_thread() lock free by making it
             look at a work info->req instead of slot->state.
Patch [4/4]: Introduce slot->hotplug_lock to serialize the hotplug
             operations.

I'd appreciate if you could please review and provide me with any comments.

Thanks,

Rajat

Rajat Jain (4):
  pciehp: Make check_link_active() non-static
  pciehp: Use link state change notifications for hot-plug and removal
  pciehp: Ensure all hotplug events are processed, even very fast ones.
  pciehp: Introduce hotplug_lock to serialize HP events on each slot

 drivers/pci/hotplug/pciehp.h      |    6 ++
 drivers/pci/hotplug/pciehp_core.c |   10 +-
 drivers/pci/hotplug/pciehp_ctrl.c |  181 ++++++++++++++++++++++++++++++++++---
 drivers/pci/hotplug/pciehp_hpc.c  |   63 +++++++++----
 4 files changed, 229 insertions(+), 31 deletions(-)

-- 
1.7.9.5


                 reply	other threads:[~2013-11-19 22:54 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=528BEC2B.4040208@gmail.com \
    --to=rajatjain.linux@gmail.com \
    --cc=linux-pci@vger.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).