From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: stable@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: please apply 'ee8bdfb6568d PCI/ASPM: Deal with missing root ports ...'
Date: Wed, 7 Mar 2018 07:23:53 -0800 [thread overview]
Message-ID: <20180307152353.GA8551@kroah.com> (raw)
In-Reply-To: <CAKv+Gu-tg16R15R9n+gz4=z0RA=RroWSYpPFYPdQnCYR_s06Aw@mail.gmail.com>
On Wed, Mar 07, 2018 at 03:06:14PM +0000, Ard Biesheuvel wrote:
> On 7 March 2018 at 15:05, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > On Wed, Mar 07, 2018 at 08:36:38AM +0000, Ard Biesheuvel wrote:
> >> On 2 March 2018 at 19:04, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> >> > L.S.,
> >> >
> >> > Please apply
> >> >
> >> > ee8bdfb6568d PCI/ASPM: Deal with missing root ports in link state handling
> >> >
> >> > to the -stable trees going back to v4.9 LTS
> >> >
> >> > It fixes an annoying boot crash that only occurs on systems with an
> >> > unusual PCIe topology, but is rather hard to diagnose for unsuspecting
> >> > users.
> >> >
> >>
> >> Apologies if I am being impatient, but .. ping?
> >
> > You are being impatient :)
> >
> >> Are you waiting for Bjorn to ack this?
> >
> > No, it's sitting behind 557 other patches I need to review for the
> > stable trees, again, please be patient.
> >
>
> OK, sorry about that :-)
No problem. Ok, now queued up, might as well get it out of the way :)
greg k-h
prev parent reply other threads:[~2018-03-07 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 19:04 please apply 'ee8bdfb6568d PCI/ASPM: Deal with missing root ports ...' Ard Biesheuvel
2018-03-07 8:36 ` Ard Biesheuvel
2018-03-07 15:05 ` Greg Kroah-Hartman
2018-03-07 15:06 ` Ard Biesheuvel
2018-03-07 15:23 ` Greg Kroah-Hartman [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=20180307152353.GA8551@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bhelgaas@google.com \
--cc=stable@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