All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: David Marchand <david.marchand@redhat.com>,
	Jerin Jacob <jerinjacobk@gmail.com>
Cc: Manish Chopra <manishc@marvell.com>,
	Gaetan Rivet <grive@u256.net>, dpdk-dev <dev@dpdk.org>,
	Igor Russkikh <irusskikh@marvell.com>,
	Rasesh Mody <rmody@marvell.com>,
	GR-Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>,
	Rosen Xu <rosen.xu@intel.com>,
	Tianfei zhang <tianfei.zhang@intel.com>,
	Heinrich Kuhn <heinrich.kuhn@netronome.com>,
	Qiming Yang <qiming.yang@intel.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v6 1/6] drivers: add generic API to find PCI extended cap
Date: Mon, 28 Sep 2020 11:32:56 +0100	[thread overview]
Message-ID: <d1006dbc-03eb-44dd-0032-776d81fa4acc@intel.com> (raw)
In-Reply-To: <CAJFAV8yMTn67Niip3gBOE=-g1d-9+D7AtfZ+nDhPouuoBfFKqA@mail.gmail.com>

On 9/28/2020 9:59 AM, David Marchand wrote:
> On Sun, Sep 27, 2020 at 2:21 PM Jerin Jacob <jerinjacobk@gmail.com> wrote:
>>
>> On Fri, Sep 25, 2020 at 5:26 PM Manish Chopra <manishc@marvell.com> wrote:
>>>
>>> By adding generic API, this patch removes individual
>>> functions/defines implemented by drivers to find extended
>>> PCI capabilities.
>>>
>>> Signed-off-by: Manish Chopra <manishc@marvell.com>
>>> Signed-off-by: Igor Russkikh <irusskikh@marvell.com>
>>> Reviewed-by: Gaetan Rivet <grive@u256.net>
>>
>> Reviewed-by: Jerin Jacob <jerinj@marvell.com>
>>
>> @Thomas Monjalon @David Marchand @Ferruh Yigit
>>
>> Othe patches in the qede series is depending on this patch, Let me
>> know, how we are planning to pull this patch? Is through main or
>> dpdk-next-net or dpdk-next-net-mrvl?
> 
> Just two small comments, that can be fixed by whoever applies it.
> 
> - The title does not reflect that we are adding an API to the pci bus.
> My suggestion is: "bus/pci: query PCI extended capabilities"
> 
> - There is an unneeded empty line added to lib/librte_pci/rte_pci.h:
> diff --git a/lib/librte_pci/rte_pci.h b/lib/librte_pci/rte_pci.h
> index 1d89651ec8..f89c7dbbea 100644
> --- a/lib/librte_pci/rte_pci.h
> +++ b/lib/librte_pci/rte_pci.h
> @@ -22,7 +22,6 @@ extern "C" {
>   #include <inttypes.h>
>   #include <sys/types.h>
> 
> -
>   /*
>    * Conventional PCI and PCI-X Mode 1 devices have 256 bytes of
>    * configuration space.  PCI-X Mode 2 and PCIe devices have 4096 bytes of
> 
> 
> The patch is reviewed by Gaëtan.
> Either through next-net or next-net-mrvl is fine to me.
> 
> I'll leave the decision to Ferruh.
> 
> 

Since other patches in the set requires Jerin's review,
@Jerin can you get the patchset to dpdk-next-net-mrvl?

  reply	other threads:[~2020-09-28 10:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25 11:55 [dpdk-dev] [PATCH v6 0/6] qede: SR-IOV PF driver support Manish Chopra
2020-09-25 11:55 ` [dpdk-dev] [PATCH v6 1/6] drivers: add generic API to find PCI extended cap Manish Chopra
2020-09-27 12:21   ` Jerin Jacob
2020-09-28  8:59     ` David Marchand
2020-09-28 10:32       ` Ferruh Yigit [this message]
2020-09-29  7:40         ` Jerin Jacob
2020-09-25 11:55 ` [dpdk-dev] [PATCH v6 2/6] net/qede: define PCI config space specific osals Manish Chopra
2020-09-25 11:55 ` [dpdk-dev] [PATCH v6 3/6] net/qede: configure VFs on hardware Manish Chopra
2020-09-25 11:55 ` [dpdk-dev] [PATCH v6 4/6] net/qede: add infrastructure support for VF load Manish Chopra
2020-09-25 11:55 ` [dpdk-dev] [PATCH v6 5/6] net/qede: initialize VF MAC and link Manish Chopra
2020-09-25 11:55 ` [dpdk-dev] [PATCH v6 6/6] net/qede: add VF FLR support Manish Chopra

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=d1006dbc-03eb-44dd-0032-776d81fa4acc@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=GR-Everest-DPDK-Dev@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=grive@u256.net \
    --cc=heinrich.kuhn@netronome.com \
    --cc=irusskikh@marvell.com \
    --cc=jerinjacobk@gmail.com \
    --cc=manishc@marvell.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=rmody@marvell.com \
    --cc=rosen.xu@intel.com \
    --cc=thomas@monjalon.net \
    --cc=tianfei.zhang@intel.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 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.