DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Deepak Kumar Jain <deepak.k.jain@intel.com>,
	pablo.de.lara.guarch@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] app/test: fix hexdump length of cipher/plaintexts
Date: Mon, 11 Jul 2016 16:09:19 +0200	[thread overview]
Message-ID: <2042764.nmHVxgRbll@xps13> (raw)
In-Reply-To: <1468167372-136814-1-git-send-email-deepak.k.jain@intel.com>

2016-07-10 17:16, Deepak Kumar Jain:
> From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> 
> Plaintexts and ciphertexts are dumped when debugging is enabled,
> using TEST_HEXDUMP. For Snow3G and KASUMI, their lengths are in bits,
> but TEST_HEXDUMP uses bytes, so lenghts are passed in bytes now.
> 
> Fixes: 47df73a1a62f ("app/test: use hexdump if debug log is enabled")
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> Signed-off-by: Deepak Kumar Jain <deepak.k.jain@intel.com>

Applied, thanks

      reply	other threads:[~2016-07-11 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09 15:05 [dpdk-dev] [PATCH] " Pablo de Lara
2016-07-10 12:55 ` Thomas Monjalon
2016-07-10 16:16 ` [dpdk-dev] [PATCH v2] " Deepak Kumar Jain
2016-07-11 14:09   ` Thomas Monjalon [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=2042764.nmHVxgRbll@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@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).