From: David Marchand <david.marchand@redhat.com>
To: "Jerin Jacob" <jerinjacobk@gmail.com>,
"Gaëtan Rivet" <grive@u256.net>,
"Manish Chopra" <manishc@marvell.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, 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 v4 1/6] drivers: add generic API to find PCI extended cap
Date: Wed, 23 Sep 2020 10:16:05 +0200 [thread overview]
Message-ID: <CAJFAV8yPRwP+H11QA5KWaAiEb6rB-9HO2sAaCQK7NDvD=xn1Yg@mail.gmail.com> (raw)
In-Reply-To: <CALBAE1OShmxQj7KWZaYEapasn3PyZTm_O3jqSVkG8x15+s74uQ@mail.gmail.com>
On Tue, Sep 22, 2020 at 9:33 PM Jerin Jacob <jerinjacobk@gmail.com> wrote:
>
> On Tue, Jul 28, 2020 at 4:06 AM Gaëtan Rivet <grive@u256.net> wrote:
> >
> > On 27/07/20 15:03 -0700, Manish Chopra 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>
> >
> > LGTM,
> > Reviewed-by: Gaetan Rivet <grive@u256.net>
>
> Gaetan Acked this change.
> This patch has dependency on other qede patches in the series.
I can see a v4 and v5 series.
https://patchwork.dpdk.org/project/dpdk/list/?series=11335
https://patchwork.dpdk.org/project/dpdk/list/?series=11421
The v5 has no review tag and the pci patch had a comment from Nithin.
https://patchwork.dpdk.org/patch/75042/#117363
>
> Hi Thomas, David, Ferruh,
>
> Should I take this patch through next-net-mrvl. if not, Could you
> merge this patch to next-net or main branch so that i can take the
> remaining patches in this series.
Let's first sort this out.
Thanks.
--
David Marchand
next prev parent reply other threads:[~2020-09-23 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 22:03 [dpdk-dev] [PATCH v4 0/6] qede: SR-IOV PF driver support Manish Chopra
2020-07-27 22:03 ` [dpdk-dev] [PATCH v4 1/6] drivers: add generic API to find PCI extended cap Manish Chopra
2020-07-27 22:35 ` Gaëtan Rivet
2020-09-22 19:33 ` Jerin Jacob
2020-09-23 8:16 ` David Marchand [this message]
2020-09-23 8:35 ` [dpdk-dev] [EXT] " Igor Russkikh
2020-07-27 22:03 ` [dpdk-dev] [PATCH v4 2/6] net/qede: define PCI config space specific osals Manish Chopra
2020-07-27 22:03 ` [dpdk-dev] [PATCH v4 3/6] net/qede: configure VFs on hardware Manish Chopra
2020-07-27 22:03 ` [dpdk-dev] [PATCH v4 4/6] net/qede: add infrastructure support for VF load Manish Chopra
2020-07-27 22:03 ` [dpdk-dev] [PATCH v4 5/6] net/qede: initialize VF MAC and link Manish Chopra
2020-07-27 22:03 ` [dpdk-dev] [PATCH v4 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='CAJFAV8yPRwP+H11QA5KWaAiEb6rB-9HO2sAaCQK7NDvD=xn1Yg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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 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).