From: Greg KH <gregkh@linuxfoundation.org>
To: Vecu Bosseur <vecu.bosseur@gmail.com>
Cc: linux-pci@vger.kernel.org, linux@vger.kernel.org, helgaas@kernel.org
Subject: Re: PCI: Don't attempt to claim shadow copies of ROM
Date: Tue, 15 Nov 2016 15:50:54 +0100 [thread overview]
Message-ID: <20161115145054.GA17120@kroah.com> (raw)
In-Reply-To: <CACivvv2UHkqPCj+jzzFGdD-uqDfKgDTsvBRLNRdzeqwWHcYo4Q@mail.gmail.com>
On Tue, Nov 15, 2016 at 01:53:39PM +0100, Vecu Bosseur wrote:
> Hello,
>
> Upstream commit 16d917b130d782b94fa02afc7bdf0d4aae689da4 ( PCI: Don't
> attempt to claim shadow copies of ROM ) didn't make it into Greg's
> stable 4.8.8 point release. Was this expected ?
Yes, because 4.8.8-rc1 came out before that commit was in a -rc release
done by Linus. I can't go back in time to add stuff to 4.8.8...
> When will this fix be picked up ? On next point release or on 4.9
> final release ?
It will be in one of the next few releases, please be patient.
thanks,
greg k-h
prev parent reply other threads:[~2016-11-15 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 12:53 PCI: Don't attempt to claim shadow copies of ROM Vecu Bosseur
2016-11-15 14:50 ` Greg KH [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=20161115145054.GA17120@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@vger.kernel.org \
--cc=vecu.bosseur@gmail.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).