linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rric@kernel.org (Robert Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] PCI: Use Cavium assigned hardware ID for ThunderX host controller
Date: Mon, 20 Mar 2017 11:49:46 +0100	[thread overview]
Message-ID: <20170320104946.GL4906@rric.localdomain> (raw)
In-Reply-To: <1489564155-3881-2-git-send-email-tn@semihalf.com>

Bjorn,

On 15.03.17 08:49:14, Tomasz Nowicki wrote:
> "CAV" is the only PNP/ACPI hardware ID vendor prefix assigned to Cavium
> so fix this as it should be from day one.
> 
> Signed-off-by: Tomasz Nowicki <tn@semihalf.com>

there is no firmware with 'THRX0002', so tagging this as
stable. Tested with latest firmware.

Fixes: 44f22bd91e88 ("PCI: Add MCFG quirks for Cavium ThunderX pass2.x host controller")
Cc: <stable@vger.kernel.org> # v4.10
Tested-by: Robert Richter <rrichter@cavium.com>
Acked-by: Robert Richter <rrichter@cavium.com>

Please apply.

Thanks,

-Robert

  reply	other threads:[~2017-03-20 10:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15  7:49 [PATCH 0/2] ThunderX external PCI fixes for legacy&new ACPI firmware Tomasz Nowicki
2017-03-15  7:49 ` [PATCH 1/2] PCI: Use Cavium assigned hardware ID for ThunderX host controller Tomasz Nowicki
2017-03-20 10:49   ` Robert Richter [this message]
2017-03-15  7:49 ` [PATCH 2/2] PCI: Add legacy firmware support for Cavium " Tomasz Nowicki
2017-03-20 11:02   ` Robert Richter
2017-03-24 15:55   ` Tomasz Nowicki
2017-03-28 19:21   ` Tomasz Nowicki
2017-03-28 19:28     ` Tomasz Nowicki
2017-03-21 17:43 ` [PATCH 0/2] ThunderX external PCI fixes for legacy&new ACPI firmware Bjorn Helgaas
2017-03-22 14:19   ` Tomasz Nowicki

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=20170320104946.GL4906@rric.localdomain \
    --to=rric@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).