From: Rami Rosen <ramirose@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Pablo De Lara Guarch <pablo.de.lara.guarch@intel.com>,
dev <dev@dpdk.org>,
tomaszx.jozwiak@intel.com
Subject: Re: [dpdk-dev] [PATCH] app/compress-perf: call generic strlcpy
Date: Mon, 25 Feb 2019 08:22:37 +0200 [thread overview]
Message-ID: <CAHLOa7Q4jfACvUZPMd7dwo=F4jW-RzZyz=8HOUNZRWPeZRkA1g@mail.gmail.com> (raw)
In-Reply-To: <20190224224201.26224-1-thomas@monjalon.net>
Checked on Fedora 28
Reviewed-by: Rami Rosen <ramirose at gmail.com>
On Mon, Feb 25, 2019 at 12:42 AM Thomas Monjalon <thomas@monjalon.net>
wrote:
> The call to strlcpy uses either libc, libbsd or internal rte_strlcpy.
> No need to call the DPDK flavor explictly.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> app/test-compress-perf/comp_perf_options_parse.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/app/test-compress-perf/comp_perf_options_parse.c
> b/app/test-compress-perf/comp_perf_options_parse.c
> index 66eb81fc59..d2b208de35 100644
> --- a/app/test-compress-perf/comp_perf_options_parse.c
> +++ b/app/test-compress-perf/comp_perf_options_parse.c
> @@ -373,7 +373,7 @@ parse_driver_name(struct comp_test_data *test_data,
> const char *arg)
> if (strlen(arg) > (sizeof(test_data->driver_name) - 1))
> return -1;
>
> - rte_strlcpy(test_data->driver_name, arg,
> + strlcpy(test_data->driver_name, arg,
> sizeof(test_data->driver_name));
>
> return 0;
> @@ -385,7 +385,7 @@ parse_test_file(struct comp_test_data *test_data,
> const char *arg)
> if (strlen(arg) > (sizeof(test_data->input_file) - 1))
> return -1;
>
> - rte_strlcpy(test_data->input_file, arg,
> sizeof(test_data->input_file));
> + strlcpy(test_data->input_file, arg, sizeof(test_data->input_file));
>
> return 0;
> }
> --
> 2.20.1
>
>
--
regards,
Rami Rosen
next prev parent reply other threads:[~2019-02-25 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 22:42 Thomas Monjalon
2019-02-25 6:22 ` Rami Rosen [this message]
2019-02-25 15:51 ` Ferruh Yigit
2019-03-13 13:21 ` Jozwiak, TomaszX
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='CAHLOa7Q4jfACvUZPMd7dwo=F4jW-RzZyz=8HOUNZRWPeZRkA1g@mail.gmail.com' \
--to=ramirose@gmail.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas@monjalon.net \
--cc=tomaszx.jozwiak@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).