From: "Gaëtan Rivet" <grive@u256.net>
To: Manish Chopra <manishc@marvell.com>
Cc: jerinjacobk@gmail.com, jerinj@marvell.com,
ferruh.yigit@intel.com, dev@dpdk.org, irusskikh@marvell.com,
rmody@marvell.com, GR-Everest-DPDK-Dev@marvell.com,
rosen.xu@intel.com, tianfei.zhang@intel.com,
heinrich.kuhn@netronome.com, qiming.yang@intel.com,
qi.z.zhang@intel.com
Subject: Re: [dpdk-dev] [PATCH v4 1/6] drivers: add generic API to find PCI extended cap
Date: Tue, 28 Jul 2020 00:35:40 +0200 [thread overview]
Message-ID: <20200727223540.g253dv5qmyp7ljmb@u256.net> (raw)
In-Reply-To: <20200727220341.29084-2-manishc@marvell.com>
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>
--
Gaëtan
next prev parent reply other threads:[~2020-07-27 22:36 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 [this message]
2020-09-22 19:33 ` Jerin Jacob
2020-09-23 8:16 ` David Marchand
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=20200727223540.g253dv5qmyp7ljmb@u256.net \
--to=grive@u256.net \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=heinrich.kuhn@netronome.com \
--cc=irusskikh@marvell.com \
--cc=jerinj@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=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).