linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Micah Parrish <micah.parrish@hpe.com>
Cc: helgaas@kernel.org, linux-pci@vger.kernel.org, linux@yadro.com,
	s.miroshnichenko@yadro.com
Subject: Re: [PATCH v2] PCI: pciehp: Fix re-enabling the slot marked for safe removal
Date: Wed, 10 Apr 2019 10:33:12 +0200	[thread overview]
Message-ID: <20190410083312.uvye5ira3w47cj2v@wunner.de> (raw)
In-Reply-To: <e11b4d88-f20d-9989-c249-2f235ef0dc28@hpe.com>

On Tue, Apr 09, 2019 at 05:41:24PM -0600, Micah Parrish wrote:
> Because this bug affects our Proliant nvme hardware, I would like to request
> the patch be merged to 5.1 and 4.19 longterm.
> 
> I have filed kernel BZ https://bugzilla.kernel.org/show_bug.cgi?id=203237

Thanks for the bug report and sorry for the breakage.

The patch has already been committed to Bjorn's pci/hotplug branch
and is marked for stable, hence will appear in the releases you've
mentioned above in about 5 weeks.  If you need it in mainline earlier
I guess Bjorn could cherry-pick the commit onto his for-linus branch
for inclusion in v5.1, that's his call.

Thanks,

Lukas

  reply	other threads:[~2019-04-10  8:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 12:05 [PATCH v2] PCI: pciehp: Fix re-enabling the slot marked for safe removal Sergey Miroshnichenko
2019-03-12 12:20 ` Lukas Wunner
2019-03-13 13:42   ` Sergey Miroshnichenko
2019-04-04 19:44 ` Bjorn Helgaas
2019-04-08 19:55 ` Bjorn Helgaas
2019-04-09 23:41   ` Micah Parrish
2019-04-10  8:33     ` Lukas Wunner [this message]
2019-04-10 21:22     ` Bjorn Helgaas
2019-04-10  8:26   ` Lukas Wunner

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=20190410083312.uvye5ira3w47cj2v@wunner.de \
    --to=lukas@wunner.de \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@yadro.com \
    --cc=micah.parrish@hpe.com \
    --cc=s.miroshnichenko@yadro.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).