From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] eal/linux: use strlcpy in uevent parsing
Date: Mon, 23 Apr 2018 15:15:11 +0100 [thread overview]
Message-ID: <20180423141511.GA105536@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20180417122329.19492-1-thomas@monjalon.net>
On Tue, Apr 17, 2018 at 02:23:29PM +0200, Thomas Monjalon wrote:
> Support of strlcpy has recently been added to DPDK.
>
> This replacement has been generated by the coccinelle script:
> devtools/cocci.sh devtools/cocci/strlcpy.cocci
>
> Fixes: 0d0f478d0483 ("eal/linux: add uevent parse and process")
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
LGTM
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2018-04-23 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 11:57 [dpdk-dev] [PATCH] " Thomas Monjalon
2018-04-17 12:23 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2018-04-23 14:15 ` Bruce Richardson [this message]
2018-04-23 14:23 ` 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=20180423141511.GA105536@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).