All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Sebastian, Selwin" <Selwin.Sebastian@amd.com>,
	"Namburu, Chandu-babu" <chandu@amd.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>
Cc: "Arsalan_Awan@mentor.com" <Arsalan_Awan@mentor.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v2] net/axgbe: use PCI root complex device to distinguish AMD hardware
Date: Mon, 17 Jan 2022 14:07:57 +0000	[thread overview]
Message-ID: <79edf769-10ad-3c00-a33c-09a8b80cd7f2@intel.com> (raw)
In-Reply-To: <DM4PR12MB505500CAE4377F3EEFCB2D4E8D579@DM4PR12MB5055.namprd12.prod.outlook.com>

On 1/17/2022 10:29 AM, Sebastian, Selwin wrote:

<...>

> -----Original Message-----
> From: Namburu, Chandu-babu <chandu@amd.com>
> Sent: Thursday, December 2, 2021 9:41 PM
> To: dev@dpdk.org; david.marchand@redhat.com
> Cc: Sebastian, Selwin <Selwin.Sebastian@amd.com>; Arsalan_Awan@mentor.com; ferruh.yigit@intel.com; Namburu, Chandu-babu <chandu@amd.com>; stable@dpdk.org
> Subject: [PATCH v2] net/axgbe: use PCI root complex device to distinguish AMD hardware
> 
> "bus/pci: optimize bus scan" broke axgbe on V1000/R1000.
> RV root complex pci device does not have any kernel driver assigned so it is removed from pci scan list which is used in
> "net/axgbe: add a HW quirk for register definitions".
> 
> Get root complex device id directly from pci sysfs instead of pci scan list.
> 
> Fixes: 991e0b1dbc4a (net/axgbe: add a HW quirk for register definitions)
> Cc: stable@dpdk.org
> 
> Signed-off-by: Chandubabu Namburu <chandu@amd.com>
> 
> Acked-by: Selwin Sebastian <selwin.sebastian@amd.com>
> 

Applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2022-01-17 14:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 10:24 [PATCH v1] net/axgbe: use PCI root complex device to distinguish AMD hardware Chandubabu Namburu
2021-12-01  8:45 ` Awan, Arsalan
2021-12-01  9:00 ` David Marchand
2021-12-02  5:53   ` Namburu, Chandu-babu
2021-12-02 16:10 ` [PATCH v2] " Chandubabu Namburu
2021-12-22  9:27   ` Namburu, Chandu-babu
2022-01-10  6:38     ` Namburu, Chandu-babu
2022-01-17  5:40       ` Sebastian, Selwin
2022-01-17 10:22         ` Ferruh Yigit
2022-01-17 10:30           ` Sebastian, Selwin
2022-01-17 10:29         ` Sebastian, Selwin
2022-01-17 14:07           ` Ferruh Yigit [this message]

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=79edf769-10ad-3c00-a33c-09a8b80cd7f2@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=Arsalan_Awan@mentor.com \
    --cc=Selwin.Sebastian@amd.com \
    --cc=chandu@amd.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.