From: Jon Masters <jcm@jonmasters.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: David Daney <ddaney@caviumnetworks.com>,
Tomasz Nowicki <tn@semihalf.com>,
David Daney <ddaney.cavm@gmail.com>,
Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>,
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
Date: Wed, 22 Mar 2017 12:25:39 -0400 [thread overview]
Message-ID: <51ba853c-f543-b21b-c25f-b56d77746f92@jonmasters.org> (raw)
In-Reply-To: <20170322144820.GA16556@bhelgaas-glaptop.roam.corp.google.com>
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 ;)
Jon.
next prev parent reply other threads:[~2017-03-22 16:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 16:25 [PATCH] PCI: ACPI: Fix ThunderX PEM initialization Vadim Lomovtsev
2017-01-30 17:39 ` David Daney
2017-01-30 21:12 ` Bjorn Helgaas
2017-01-31 10:28 ` Vadim Lomovtsev
2017-01-31 14:25 ` Bjorn Helgaas
2017-01-31 14:57 ` Vadim Lomovtsev
2017-01-31 20:31 ` Bjorn Helgaas
2017-02-01 12:53 ` Vadim Lomovtsev
2017-02-01 15:18 ` Bjorn Helgaas
2017-02-01 15:34 ` Vadim Lomovtsev
2017-03-15 11:14 ` Jon Masters
2017-03-15 11:33 ` Vadim Lomovtsev
2017-03-16 14:32 ` Jon Masters
2017-03-16 16:25 ` David Daney
2017-03-21 11:38 ` Jon Masters
2017-03-21 13:47 ` Bjorn Helgaas
2017-03-21 14:17 ` Tomasz Nowicki
2017-03-21 14:56 ` David Daney
2017-03-22 14:28 ` Jon Masters
2017-03-22 14:48 ` Bjorn Helgaas
2017-03-22 16:25 ` Jon Masters [this message]
2017-03-22 16:34 ` Bjorn Helgaas
2017-03-23 22:14 ` Bjorn Helgaas
2017-03-23 22:16 ` Jon Masters
2017-03-21 17:45 ` Bjorn Helgaas
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=51ba853c-f543-b21b-c25f-b56d77746f92@jonmasters.org \
--to=jcm@jonmasters.org \
--cc=David.Daney@cavium.com \
--cc=Vadim.Lomovtsev@caviumnetworks.com \
--cc=bhelgaas@google.com \
--cc=ddaney.cavm@gmail.com \
--cc=ddaney@caviumnetworks.com \
--cc=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=stemerkhanov@CAVIUMNETWORKS.onmicrosoft.com \
--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).