DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: Andrew Rybchenko <arybchenko@solarflare.com>,
	Rami Rosen <ramirose@gmail.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] ethdev: use strlcpy
Date: Wed, 13 Mar 2019 18:17:37 +0000	[thread overview]
Message-ID: <ac25303f-bca2-0ec0-87b5-c2bad6eda64f@intel.com> (raw)
In-Reply-To: <20190228224754.26511-1-stephen@networkplumber.org>

On 2/28/2019 10:47 PM, Stephen Hemminger wrote:
> A couple of places in ethdev are clearer if strlcpy is used.
> 
> Stephen Hemminger (2):
>   ethdev: replace snprintf with strlcpy
>   ethdev: use strlcpy instead of snprintf on initialization

Series applied to dpdk-next-net/master, thanks.

(2/2 updated as suggested while merging.)

      parent reply	other threads:[~2019-03-13 18:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 22:47 Stephen Hemminger
2019-02-28 22:47 ` [dpdk-dev] [PATCH 1/2] ethdev: replace snprintf with strlcpy Stephen Hemminger
2019-03-01  7:40   ` Andrew Rybchenko
2019-02-28 22:47 ` [dpdk-dev] [PATCH 2/2] ethdev: use strlcpy instead of snprintf on initialization Stephen Hemminger
2019-03-01  6:54   ` Rami Rosen
2019-03-01  7:48   ` Andrew Rybchenko
2019-03-01 18:42     ` Stephen Hemminger
2019-03-04  9:11       ` Andrew Rybchenko
2019-03-04 19:12         ` Stephen Hemminger
2019-03-06 15:55           ` Ferruh Yigit
2019-03-13 18:17 ` Ferruh Yigit [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=ac25303f-bca2-0ec0-87b5-c2bad6eda64f@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ramirose@gmail.com \
    --cc=stephen@networkplumber.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).