All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Sinan Kaya <okaya@kernel.org>
Subject: [PATCH v7 0/1] PCI: Handle conflict between hotplug and error handling
Date: Sun,  5 Aug 2018 15:51:35 -0700	[thread overview]
Message-ID: <20180805225136.5800-1-okaya@kernel.org> (raw)

Lukas:
'Your patch "[PATCH v6 1/1] PCI: pciehp: Ignore link events when there
is a fatal error pending" only checks once for a pending fatal error,
it should poll until either the fatal error is gone or a timeout is
hit.  If the fatal error is gone and the link is up, you can just return
from pciehp_handle_presence_or_link_change().  Else (in the timeout case)
fall back to the normal handling of a Link Down, i.e. let it bring down
the slot.'


Sinan Kaya (1):
  PCI: pciehp: Ignore link events when there is a fatal error pending

 drivers/pci/hotplug/pciehp_ctrl.c | 19 ++++++++++
 drivers/pci/pci.h                 |  2 ++
 drivers/pci/pcie/err.c            | 60 +++++++++++++++++++++++++++++++
 3 files changed, 81 insertions(+)

-- 
2.17.1

             reply	other threads:[~2018-08-06  0:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-05 22:51 Sinan Kaya [this message]
2018-08-05 22:51 ` [PATCH v7 1/1] PCI: pciehp: Ignore link events when there is a fatal error pending Sinan Kaya
2018-08-06  7:51   ` poza
2018-08-06  9:26     ` Lukas Wunner
2018-08-06 14:55       ` poza
2018-08-06 15:04         ` Sinan Kaya
2018-08-06 15:06           ` Sinan Kaya
2018-08-06 15:12             ` poza
2018-08-06 16:34               ` Sinan Kaya
2018-08-06 16:44             ` Lukas Wunner
2018-08-06 16:49               ` Sinan Kaya
2018-08-06 17:03                 ` Sinan Kaya
2018-08-06 17:05                 ` Lukas Wunner
2018-08-06 17:09                   ` Sinan Kaya
2018-08-06  9:30   ` Lukas Wunner
2018-09-04 18:18 ` [PATCH v7 0/1] PCI: Handle conflict between hotplug and error handling Bjorn Helgaas
2018-09-04 18:28   ` Sinan Kaya

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=20180805225136.5800-1-okaya@kernel.org \
    --to=okaya@kernel.org \
    --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 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.