From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: tn@semihalf.com, Vadim.Lomovtsev@caviumnetworks.com,
Robert Richter <rrichter@cavium.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
stable-commits@vger.kernel.org
Subject: Re: Patch "PCI: thunder-pem: Add legacy firmware support for Cavium ThunderX host controller" has been added to the 4.10-stable tree
Date: Sun, 9 Apr 2017 10:24:27 +0200 [thread overview]
Message-ID: <20170409082427.GA21685@kroah.com> (raw)
In-Reply-To: <CAErSpo79LnBKZET_k48-VypdeLZxWYrW9X5wto56KodQkjLPJw@mail.gmail.com>
On Sat, Apr 08, 2017 at 11:35:56AM -0500, Bjorn Helgaas wrote:
> On Thu, Apr 6, 2017 at 2:27 AM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Mon, Apr 03, 2017 at 07:03:53AM -0700, Bjorn Helgaas wrote:
> >> I think there's an issue with this one that will be resolved this
> >> week. It would be better to wait for that and add both patches to the
> >> stable tree at the same time.
> >
> > Ok, I'll drop this one now, can someone remind stable@ when the fix goes
> > in to add this patch, and the new one?
>
> This patch (9abb27c7594a ("PCI: thunder-pem: Add legacy firmware
> support for Cavium ThunderX host controller")) and feb199ebef48 ("PCI:
> thunder-pem: Fix legacy firmware PEM-specific resources"), which
> appeared in Linus' tree yesterday, should be merged to stable
> together.
Thanks for letting me know, now all queued up.
greg k-h
next prev parent reply other threads:[~2017-04-09 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 12:40 Patch "PCI: thunder-pem: Add legacy firmware support for Cavium ThunderX host controller" has been added to the 4.10-stable tree gregkh
2017-04-03 14:03 ` Bjorn Helgaas
2017-04-06 7:27 ` Greg Kroah-Hartman
2017-04-08 16:35 ` Bjorn Helgaas
2017-04-09 8:24 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-09 8:25 gregkh
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=20170409082427.GA21685@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Vadim.Lomovtsev@caviumnetworks.com \
--cc=bhelgaas@google.com \
--cc=rrichter@cavium.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tn@semihalf.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).