patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Uttarwar, Sunil Prakashrao" <SunilPrakashrao.Uttarwar@amd.com>,
	David Marchand <david.marchand@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"Somalapuram, Amaranath" <Amaranath.Somalapuram@amd.com>,
	"Sebastian, Selwin" <Selwin.Sebastian@amd.com>
Subject: RE: [PATCH v2] crypto/ccp: fix PCI probing
Date: Sat, 11 Mar 2023 18:49:58 +0000	[thread overview]
Message-ID: <CO6PR18MB4484CE01A7004FB0BE05FF14D8BB9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <PH7PR12MB6694DC7678214845B31DBE2F92B69@PH7PR12MB6694.namprd12.prod.outlook.com>

> 
> Acked-by: Sunil Uttarwar <sunilprakashrao.uttarwar@amd.com>
> 
> Subject: [PATCH v2] crypto/ccp: fix PCI probing
> 
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
> 
> 
> This driver has been converted from a vdev driver to a pci driver some time ago.
> This conversion is buggy as it tries to probe any pci devices present on a system
> for *each* probe request from the PCI bus.
> 
> Rely on the passed pci device and only probe what is requested.
> 
> While at it:
> - stop copying the pci device object content into a local private copy,
> - rely on the PCI identifier and remove internal ccp_device_version
>   identifier,
> - ccp_list can be made static,
> 
> With this done, all the code parsing Linux sysfs can be dropped.
> 
> Fixes: 889317b7ecb3 ("crypto/ccp: convert driver from vdev to PCI")
> Cc: stable@dpdk.org
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>

Applied to dpdk-next-crypto.

Thanks.

      reply	other threads:[~2023-03-11 18:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220909150411.3702860-1-david.marchand@redhat.com>
2022-09-09 15:04 ` [PATCH 1/4] crypto/ccp: remove some printf David Marchand
2022-09-09 15:04 ` [PATCH 2/4] crypto/ccp: remove some dead code for UIO David Marchand
2022-09-09 15:04 ` [PATCH 3/4] crypto/ccp: fix IOVA handling David Marchand
2022-09-09 15:04 ` [PATCH 4/4] crypto/ccp: fix PCI probing David Marchand
     [not found] ` <20221004095132.198777-1-david.marchand@redhat.com>
2022-10-04  9:51   ` [PATCH v2 1/4] crypto/ccp: remove some printf David Marchand
2023-01-13 11:58     ` Uttarwar, Sunil Prakashrao
2023-01-30 18:42     ` [EXT] " Akhil Goyal
2022-10-04  9:51   ` [PATCH v2 2/4] crypto/ccp: remove some dead code for UIO David Marchand
2023-01-13 12:00     ` Uttarwar, Sunil Prakashrao
2022-10-04  9:51   ` [PATCH v2 3/4] crypto/ccp: fix IOVA handling David Marchand
2023-01-13 12:00     ` Uttarwar, Sunil Prakashrao
2022-10-04  9:51   ` [PATCH v2 4/4] crypto/ccp: fix PCI probing David Marchand
2023-03-02 11:43 ` [PATCH v2] " David Marchand
2023-03-06 12:05   ` Uttarwar, Sunil Prakashrao
2023-03-11 18:49     ` Akhil Goyal [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=CO6PR18MB4484CE01A7004FB0BE05FF14D8BB9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=Amaranath.Somalapuram@amd.com \
    --cc=Selwin.Sebastian@amd.com \
    --cc=SunilPrakashrao.Uttarwar@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 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).