DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Fu, Patrick" <patrick.fu@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Xia, Chenbo" <chenbo.xia@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] vhost: fix async callback return type define
Date: Tue, 28 Jul 2020 10:15:55 +0000	[thread overview]
Message-ID: <DM5PR1101MB2169BB3F98176633901477F984730@DM5PR1101MB2169.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2faeef8f-01e0-aaee-8105-7027c49e4589@redhat.com>

Hi Maxime,

> -----Original Message-----
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
> Sent: Tuesday, July 28, 2020 5:10 PM
> To: Fu, Patrick <patrick.fu@intel.com>; dev@dpdk.org; Xia, Chenbo
> <chenbo.xia@intel.com>
> Subject: Re: [PATCH v1] vhost: fix async callback return type define
> 
> 
> 
> On 7/23/20 7:39 AM, patrick.fu@intel.com wrote:
> > From: Patrick Fu <patrick.fu@intel.com>
> >
> >  	 * @return
> > -	 *  -1 on failure, number of iov segments completed on success
> > +	 *  number of iov segments completed on success
> Ditto
> 
> >  	 */
> > -	int (*check_completed_copies)(int vid, uint16_t queue_id,
> > +	uint32_t (*check_completed_copies)(int vid, uint16_t queue_id,
> >  		struct rte_vhost_async_status *opaque_data,
> >  		uint16_t max_packets);
> >  };
> >
> 
> Other than that:
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> 
> I can fixup the comments while applying if you agree with it.
> 

Yes, I think removing "on success" is correct there.

Thanks,

Patrick


  reply	other threads:[~2020-07-28 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23  5:39 patrick.fu
2020-07-27 12:52 ` Xia, Chenbo
2020-07-28  9:10 ` Maxime Coquelin
2020-07-28 10:15   ` Fu, Patrick [this message]
2020-07-28 15:26 ` Maxime Coquelin

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=DM5PR1101MB2169BB3F98176633901477F984730@DM5PR1101MB2169.namprd11.prod.outlook.com \
    --to=patrick.fu@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.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).