DPDK patches and discussions
 help / color / mirror / Atom feed
From: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	"Van Haaren, Harry" <harry.van.haaren@intel.com>,
	"Ray Kinsella" <mdr@ashroe.eu>,
	Neil Horman <nhorman@tuxdriver.com>,
	"Rao, Nikhil" <nikhil.rao@intel.com>,
	"Carrillo, Erik G" <erik.g.carrillo@intel.com>,
	"Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>,
	"pbhagavatula@marvell.com" <pbhagavatula@marvell.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	mattias.ronnblom <mattias.ronnblom@ericsson.com>,
	"Mccarthy, Peter" <peter.mccarthy@intel.com>
Subject: Re: [dpdk-dev] [PATCH] usertools/devbind: add dlb
Date: Mon, 26 Apr 2021 13:00:47 +0000	[thread overview]
Message-ID: <SN6PR11MB310306FCB7FE665342A20B149E429@SN6PR11MB3103.namprd11.prod.outlook.com> (raw)
In-Reply-To: <ece8e927-7a23-4ebe-8121-81fc10c08175@www.fastmail.com>



> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Sunday, April 25, 2021 10:53 AM
> To: McDaniel, Timothy <timothy.mcdaniel@intel.com>
> Cc: dev@dpdk.org; Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Van
> Haaren, Harry <harry.van.haaren@intel.com>; Ray Kinsella <mdr@ashroe.eu>;
> Neil Horman <nhorman@tuxdriver.com>; Rao, Nikhil <nikhil.rao@intel.com>;
> Carrillo, Erik G <erik.g.carrillo@intel.com>; Gujjar, Abhinandan S
> <abhinandan.gujjar@intel.com>; pbhagavatula@marvell.com; Hemant Agrawal
> <hemant.agrawal@nxp.com>; mattias.ronnblom
> <mattias.ronnblom@ericsson.com>; Mccarthy, Peter
> <peter.mccarthy@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] usertools/devbind: add dlb
> 
> Timothy McDaniel:
> > --- a/usertools/dpdk-devbind.py
> > +++ b/usertools/dpdk-devbind.py
> > @@ -59,11 +59,13 @@
> >                   'SVendor': None, 'SDevice': None}
> >  intel_ntb_icx = {'Class': '06', 'Vendor': '8086', 'Device': '347e',
> >                   'SVendor': None, 'SDevice': None}
> > +intel_dlb = {'Class': '0b', 'Vendor': '8086', 'Device': '270b,2710,2714',
> > +             'SVendor': None, 'SDevice': None}
> >
> >  network_devices = [network_class, cavium_pkx, avp_vnic, ifpga_class]
> >  baseband_devices = [acceleration_class]
> >  crypto_devices = [encryption_class, intel_processor_class]
> > -eventdev_devices = [cavium_sso, cavium_tim, octeontx2_sso]
> > +eventdev_devices = [cavium_sso, cavium_tim, octeontx2_sso, intel_dlb]
> 
> Please try to insert new items in alphabetical order.

Thanks for the feedback, Thomas.  I will update and resubmit.

  reply	other threads:[~2021-04-26 13:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 20:04 Timothy McDaniel
2021-04-25 15:53 ` Thomas Monjalon
2021-04-26 13:00   ` McDaniel, Timothy [this message]
2021-04-26 15:34 ` [dpdk-dev] [PATCH v2 1/1] " Timothy McDaniel
2021-05-19  9:47   ` Thomas Monjalon

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=SN6PR11MB310306FCB7FE665342A20B149E429@SN6PR11MB3103.namprd11.prod.outlook.com \
    --to=timothy.mcdaniel@intel.com \
    --cc=abhinandan.gujjar@intel.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=mdr@ashroe.eu \
    --cc=nhorman@tuxdriver.com \
    --cc=nikhil.rao@intel.com \
    --cc=pbhagavatula@marvell.com \
    --cc=peter.mccarthy@intel.com \
    --cc=thomas@monjalon.net \
    /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).