From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
Kevin Traynor <ktraynor@redhat.com>
Cc: dev@dpdk.org, Reshma Pattan <reshma.pattan@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] eal: support strlcat function
Date: Tue, 16 Apr 2019 17:03:19 +0100 [thread overview]
Message-ID: <d74b85f3-14ad-48e3-72cb-86f136926056@intel.com> (raw)
Message-ID: <20190416160319.LB5bm2-4jsvaV9NlgVm9wqmw4jXSHDuWD_q5DNaufjM@z> (raw)
In-Reply-To: <20190416143715.GA1870@bricha3-MOBL.ger.corp.intel.com>
On 4/16/2019 3:37 PM, Bruce Richardson wrote:
> On Tue, Apr 16, 2019 at 03:29:52PM +0100, Kevin Traynor wrote:
>> On 17/01/2019 17:30, Bruce Richardson wrote:
>>> Add the strlcat function to DPDK to exist alongside the strlcpy one.
>>> While strncat is generally safe for use for concatenation, the API for the
>>> strlcat function is perhaps a little nicer to use, and supports truncation
>>> detection.
>>>
>>> See commit 5364de644a4b ("eal: support strlcpy function") for more
>>> details on the function selection logic, since we only should be using the
>>> DPDK-provided version when no system-provided version is present.
>>>
>>> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>>> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>>
>> Hi - I'd like to backport this to 18.11 stable branch. Not having it is
>> starting to cause build failures with backports. Let me know if any
>> objection.
>>
> Go for it! No objections here, I think it makes sense.
+1 for the backport.
next prev parent reply other threads:[~2019-04-16 16:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 12:48 [dpdk-dev] [PATCH] " Bruce Richardson
2019-01-17 10:39 ` Burakov, Anatoly
2019-01-17 11:00 ` Bruce Richardson
2019-01-17 11:55 ` Burakov, Anatoly
2019-01-17 13:10 ` Ferruh Yigit
2019-01-17 16:30 ` [dpdk-dev] [PATCH v2] " Bruce Richardson
2019-01-17 16:50 ` Ferruh Yigit
2019-01-17 17:05 ` Pattan, Reshma
2019-01-17 17:30 ` [dpdk-dev] [PATCH v3] " Bruce Richardson
2019-02-12 9:27 ` Thomas Monjalon
2019-04-16 14:29 ` Kevin Traynor
2019-04-16 14:29 ` Kevin Traynor
2019-04-16 14:37 ` Bruce Richardson
2019-04-16 14:37 ` Bruce Richardson
2019-04-16 16:03 ` Ferruh Yigit [this message]
2019-04-16 16:03 ` Ferruh Yigit
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=d74b85f3-14ad-48e3-72cb-86f136926056@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=reshma.pattan@intel.com \
--cc=stable@dpdk.org \
/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).