From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org, xiaoyun.li@intel.com
Subject: Re: [dpdk-stable] [PATCH] eal/x86: remove unused memcpy file
Date: Mon, 12 Nov 2018 00:13:53 +0100 [thread overview]
Message-ID: <14042887.bUzHa6xqD7@xps> (raw)
In-Reply-To: <d57a189d-755b-36be-0b52-bceec2f51929@intel.com>
09/11/2018 18:35, Ferruh Yigit:
> On 11/9/2018 1:46 PM, Thomas Monjalon wrote:
> > The use of rte_memcpy_ptr was removed in revert below,
> > but it was missing removing the file arch/x86/rte_memcpy.c.
> >
> > Fixes: d35cc1fe6a7a ("eal/x86: revert select optimized memcpy at run-time")
> > Cc: stable@dpdk.org
> > Cc: xiaoyun.li@intel.com
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied
prev parent reply other threads:[~2018-11-11 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 13:46 Thomas Monjalon
2018-11-09 17:35 ` Ferruh Yigit
2018-11-11 23:13 ` 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=14042887.bUzHa6xqD7@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@dpdk.org \
--cc=xiaoyun.li@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).