DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] replace bzero with memset
Date: Wed, 2 Dec 2015 08:28:50 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C863863@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1449026652-7320-1-git-send-email-stephen@networkplumber.org>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen
> Hemminger
> Sent: Wednesday, December 02, 2015 3:24 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 0/3] replace bzero with memset
> 
> The DPDK is mostly consistent about using the POSIX standard
> memset instead of bzero; but there seem to be some leftover BSD
> hold outs.
> 
> Stephen Hemminger (3):
>   test-pmd: use memset not bzero
>   xen-virt: use memset not bzero
>   qat: use memset instead of bzero
> 
>  app/test-pmd/testpmd.c                | 4 ++--
>  drivers/net/xenvirt/rte_eth_xenvirt.c | 3 ++-
>  examples/dpdk_qat/crypto.c            | 8 ++++----
>  3 files changed, 8 insertions(+), 7 deletions(-)
> 
> --
> 2.1.4

Series-Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>

  parent reply	other threads:[~2015-12-02  8:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02  3:24 Stephen Hemminger
2015-12-02  3:24 ` [dpdk-dev] [PATCH 1/3] test-pmd: use memset not bzero Stephen Hemminger
2015-12-02  3:24 ` [dpdk-dev] [PATCH 2/3] xen-virt: " Stephen Hemminger
2015-12-02  3:24 ` [dpdk-dev] [PATCH 3/3] qat: use memset instead of bzero Stephen Hemminger
2015-12-02  8:28 ` De Lara Guarch, Pablo [this message]
2015-12-06 22:51   ` [dpdk-dev] [PATCH 0/3] replace bzero with memset 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=E115CCD9D858EF4F90C690B0DCB4D8973C863863@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@dpdk.org \
    --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).