DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>
Cc: dev@dpdk.org, Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Vamsi Krishna Attunuru <vattunuru@marvell.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2] common/octeontx2: add CNF95xx SoC support
Date: Sun, 14 Jul 2019 15:44:03 +0200	[thread overview]
Message-ID: <42268880.5OJ7u2Y0nn@xps> (raw)
In-Reply-To: <BYAPR18MB24241DE2E96050F59A445FECC8F20@BYAPR18MB2424.namprd18.prod.outlook.com>

12/07/2019 14:37, Jerin Jacob Kollanukkaran:
> > -----Original Message-----
> > From: Nithin Dabilpuram <ndabilpuram@marvell.com>
> > Sent: Friday, July 12, 2019 2:56 PM
> > To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Nithin Kumar
> > Dabilpuram <ndabilpuram@marvell.com>; Vamsi Krishna Attunuru
> > <vattunuru@marvell.com>; John McNamara <john.mcnamara@intel.com>;
> > Marko Kovacevic <marko.kovacevic@intel.com>; Kiran Kumar Kokkilagadda
> > <kirankumark@marvell.com>
> > Cc: dev@dpdk.org
> > Subject: [PATCH v2] common/octeontx2: add CNF95xx SoC support
> > 
> > Update platform support of CNF95xx in documentation and also, update the
> > HW cap based on PCI subsystem id and revision id.
> > This patch also changes HW capability handling to be based on PCI Revision
> > ID. PCI Revision ID contains a unique identifier to identify chip, major and
> > minor revisions.
> > 
> > Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> 
> Acked-by: Jerin Jacob <jerinj@marvell.com>

Applied, thanks



      reply	other threads:[~2019-07-14 13:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 17:01 [dpdk-dev] [PATCH] " Nithin Dabilpuram
2019-07-11 11:56 ` Jerin Jacob Kollanukkaran
2019-07-12  9:25 ` [dpdk-dev] [PATCH v2] " Nithin Dabilpuram
2019-07-12 12:37   ` Jerin Jacob Kollanukkaran
2019-07-14 13:44     ` Thomas Monjalon [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=42268880.5OJ7u2Y0nn@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=kirankumark@marvell.com \
    --cc=marko.kovacevic@intel.com \
    --cc=ndabilpuram@marvell.com \
    --cc=vattunuru@marvell.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).