DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: Zhiyong Yang <zhiyong.yang@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH] mbuf: remove void pointer cast
Date: Mon, 22 Jan 2018 14:07:28 +0100	[thread overview]
Message-ID: <20180122130728.hzh3r3kwu6smcwx3@platinum> (raw)
In-Reply-To: <20180119101813.31450-1-zhiyong.yang@intel.com>

On Fri, Jan 19, 2018 at 06:18:13PM +0800, Zhiyong Yang wrote:
> It is unnecessary to cast from void * to struct rte_mbuf *,
> the change can make code clearer.
> 
> Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>

Acked-by: Olivier Matz <olivier.matz@6wind.com>

Zhihong, for next time please prefix the patch with "PATCH v2"
and use --in-reply-to with the message id of the first version.

Thanks
Olivier

  reply	other threads:[~2018-01-22 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 10:18 Zhiyong Yang
2018-01-22 13:07 ` Olivier Matz [this message]
2018-01-23  1:15   ` Yang, Zhiyong
2018-01-25 21:51   ` 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=20180122130728.hzh3r3kwu6smcwx3@platinum \
    --to=olivier.matz@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    --cc=zhiyong.yang@intel.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).