linux-kernel - Re: [PATCH] PCI: ACPI: Fix ThunderX PEM initialization

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 22 Mar 2017 11:34:00 -0500
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Jon Masters <jcm@...masters.org>
Cc:     David Daney <ddaney@...iumnetworks.com>,
        Tomasz Nowicki <tn@...ihalf.com>,
        David Daney <ddaney.cavm@...il.com>,
        Vadim Lomovtsev <Vadim.Lomovtsev@...iumnetworks.com>,
        David.Daney@...ium.com, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        stemerkhanov@...IUMNETWORKS.onmicrosoft.com, bhelgaas@...gle.com,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] PCI: ACPI: Fix ThunderX PEM initialization

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.