DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Charles (Chas) Williams" <ciwillia@brocade.com>, dev@dpdk.org
Cc: skhare@vmware.com
Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: avoid code duplication
Date: Wed, 5 Jul 2017 15:58:03 +0100	[thread overview]
Message-ID: <37fbaf82-215c-1afe-a4e9-f8922babb308@intel.com> (raw)
In-Reply-To: <c0fa8d64-350e-bf7c-c81b-c217189c53bc@intel.com>

On 7/5/2017 3:55 PM, Ferruh Yigit wrote:
> On 6/29/2017 8:35 PM, Charles (Chas) Williams wrote:
>> Refactor vmxnet3_post_rx_bufs() to call vmxnet3_renew_desc()
>> to update the newly allocated mbufs.  While here, relocate the
>> relevant comments to vmxnet3_renew_desc().
>>
>> Signed-off-by: Chas Williams <ciwillia@brocade.com>
> 
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2017-07-05 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 19:35 Charles (Chas) Williams
2017-07-05 14:55 ` Ferruh Yigit
2017-07-05 14:58   ` Ferruh Yigit [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=37fbaf82-215c-1afe-a4e9-f8922babb308@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ciwillia@brocade.com \
    --cc=dev@dpdk.org \
    --cc=skhare@vmware.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).