From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Pawel Wodkowski <pawelx.wodkowski@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] fix rte_memcpy() macro: avoid unused value warning
Date: Wed, 17 Dec 2014 00:50:16 +0100 [thread overview]
Message-ID: <1637016.W8b35voK5x@xps13> (raw)
In-Reply-To: <533710CFB86FA344BFBF2D6802E60286CA0168@SHSMSX101.ccr.corp.intel.com>
2014-12-16 01:57, Qiu, Michael:
> On 12/16/2014 12:55 AM, Michal Jastrzebski wrote:
> > From: Pawel Wodkowski <pawelx.wodkowski@intel.com>
> >
> > This change use statements in expressions C extension provided by gcc to avoid
> > 'value computed is not used' warning/error when size is not known at compile
> > time.
> >
> > Comments on possible side effects are welcome an tests are welcome.
> >
> > Reported-by: Qiu, Michael <michael.qiu@intel.com>
> > Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com>
>
> Acked-by: Qiu, Michael <michael.qiu@intel.com>
Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Applied with a PPC equivalent.
Thanks
--
Thomas
prev parent reply other threads:[~2014-12-16 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 16:55 Michal Jastrzebski
2014-12-16 1:57 ` Qiu, Michael
2014-12-16 23:50 ` Thomas Monjalon [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=1637016.W8b35voK5x@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=pawelx.wodkowski@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).