On Wed, Mar 22, 2017 at 11:34:00AM -0500, Bjorn Helgaas wrote:
> On Wed, Mar 22, 2017 at 12:25:39PM -0400, Jon Masters wrote:
> > On 03/22/2017 10:48 AM, Bjorn Helgaas wrote:
> > > On Wed, Mar 22, 2017 at 10:28:27AM -0400, Jon Masters wrote:
> > >> On 03/21/2017 10:56 AM, David Daney wrote:
> > >
> > >>> Yes. After all this back and forth, Cavium has decided to deploy
> > >>> firmware with "CAVxxx" as _HID.
> > >>
> > >> Great. How about a stable backport for Greg K-H? I want to make sure
> > >> that everyone running "upstream" has a chance of booting.
> > >
> > > The first patch, fee4d813850c ("PCI: Use Cavium assigned hardware ID for
> > > ThunderX host controller"), has a stable tag already.
> >
> > Thanks - I saw that after I mailed.
> >
> > > The second, 1dc94a38af89 ("PCI: Add legacy firmware support for Cavium
> > > ThunderX host controller"), does not, but I can easily add it if needed.
> >
> > I think that would be ideal. There is firmware out in the wild that
> > has neither identifier in it (for example, a bunch of folks in the
> > office bought platforms recently that don't boot upstream kernels).
> > My guys are used to just taking an upstream kernel and using that,
> > for development, and I have no intention of having the broader RH
> > org do any different from what they would do with an x86 box ;)
>
> I added the same stable tag (v4.10+) to the second patch.
I moved these from pci/host-thunder (targeted for v4.12) to for-linus so we
can get these in v4.11.
