Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964847AbdCVQeZ (ORCPT ); Wed, 22 Mar 2017 12:34:25 -0400 Received: from mail.kernel.org ([198.145.29.136]:44168 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759256AbdCVQeR (ORCPT ); Wed, 22 Mar 2017 12:34:17 -0400 Date: Wed, 22 Mar 2017 11:34:00 -0500 From: Bjorn Helgaas To: Jon Masters Cc: David Daney , Tomasz Nowicki , David Daney , Vadim Lomovtsev , David.Daney@cavium.com, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, stemerkhanov@CAVIUMNETWORKS.onmicrosoft.com, bhelgaas@google.com, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] PCI: ACPI: Fix ThunderX PEM initialization Message-ID: <20170322163359.GB24935@bhelgaas-glaptop.roam.corp.google.com> References: <20170315113323.GA28027@localhost.localdomain> <251db823-591b-483b-9c55-13c911020fd1@jonmasters.org> <48b93116-cc0f-e59d-8aa3-704052ad6759@gmail.com> <20170321134744.GA13150@bhelgaas-glaptop.roam.corp.google.com> <20170322144820.GA16556@bhelgaas-glaptop.roam.corp.google.com> <51ba853c-f543-b21b-c25f-b56d77746f92@jonmasters.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51ba853c-f543-b21b-c25f-b56d77746f92@jonmasters.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1288 Lines: 27 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.