DPDK patches and discussions
 help / color / mirror / Atom feed
From: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
To: "Eads, Gage" <gage.eads@intel.com>, Jerin Jacob <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Carrillo, Erik G" <erik.g.carrillo@intel.com>,
	"Van Haaren, Harry" <harry.van.haaren@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eventdev: add PCI probe named convenience function
Date: Wed, 16 Sep 2020 18:39:15 +0000	[thread overview]
Message-ID: <BL0PR11MB3090254A30CC7226C5AA85E09E210@BL0PR11MB3090.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB2574D6A3E7ECE77985251476F6230@SN6PR11MB2574.namprd11.prod.outlook.com>



> -----Original Message-----
> From: Eads, Gage <gage.eads@intel.com>
> Sent: Monday, September 14, 2020 3:23 PM
> To: McDaniel, Timothy <timothy.mcdaniel@intel.com>; Jerin Jacob
> <jerinj@marvell.com>
> Cc: dev@dpdk.org; Carrillo, Erik G <Erik.G.Carrillo@intel.com>; Van Haaren,
> Harry <harry.van.haaren@intel.com>
> Subject: RE: [PATCH] eventdev: add PCI probe named convenience function
> 
> <snip>
> 
> >  /**
> >   * @internal
> > + * Wrapper for use by pci drivers as a .probe function to attach to a event
> > + * interface.
> > + */
> > +static inline int
> > +rte_event_pmd_pci_probe(struct rte_pci_driver *pci_drv,
> > +			    struct rte_pci_device *pci_dev,
> > +			    size_t private_data_size,
> > +			    eventdev_pmd_pci_callback_t devinit)
> > +{
> > +	char eventdev_name[RTE_EVENTDEV_NAME_MAX_LEN];
> > +
> > +
> 
> Two blank lines -- DPDK coding style doesn't forbid this as far as I know
> (LINE_SPACING is ignored in checkpatch), but just an FYI in case this was
> unintentional.

Fixed.  Will be available in V2 patch-set.

> 
> > +	rte_pci_device_name(&pci_dev->addr, eventdev_name,
> > +			sizeof(eventdev_name));
> > +
> > +	return rte_event_pmd_pci_probe_named(pci_drv,
> > +					     pci_dev,
> > +					     private_data_size,
> > +					     devinit,
> > +					    (const char *)eventdev_name);
> 
> Nit: the cast is unnecessary, the conversion will happen implicitly without it.
> 

Fixed.  Will be available in V2 patch-set.

> With that,
> Reviewed-by: Gage Eads <gage.eads@intel.com>

  reply	other threads:[~2020-09-16 18:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 17:04 Timothy McDaniel
2020-09-14 20:22 ` Eads, Gage
2020-09-16 18:39   ` McDaniel, Timothy [this message]
2020-10-12 18:42 ` Timothy McDaniel
2020-10-14  9:31   ` Kinsella, Ray
2020-10-14 15:37     ` Eads, Gage
2020-10-16 11:26       ` Kinsella, Ray
2020-10-12 19:01 ` Timothy McDaniel
2020-10-13 18:47   ` Jerin Jacob
2020-10-14 17:35 ` [dpdk-dev] [PATCH v4] " Timothy McDaniel
2020-10-14 21:41 ` [dpdk-dev] [PATCH v5] " Timothy McDaniel
2020-10-15 14:16 ` [dpdk-dev] [PATCH v6] " Timothy McDaniel
2020-10-15 18:49   ` Jerin Jacob

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=BL0PR11MB3090254A30CC7226C5AA85E09E210@BL0PR11MB3090.namprd11.prod.outlook.com \
    --to=timothy.mcdaniel@intel.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=gage.eads@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=jerinj@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).