DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] drivers/crypto: fix drivers to use ring size function
Date: Mon, 27 Mar 2017 23:58:28 +0200	[thread overview]
Message-ID: <3836698.qL7ye4rpXD@xps13> (raw)
In-Reply-To: <20170327145440.9648-1-bruce.richardson@intel.com>

2017-03-27 15:54, Bruce Richardson:
> Rather than reading the size directly from the ring structure, use the
> dedicated ring function for that purpose.
> Previous commits to do this only did so for the null crypto driver which
> was the only one compiled in by default, but all other drivers need to be
> similarly updated.
> 
> Fixes: b11c78a2e0c6 ("crypto/null: use ring size function")
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>

Applied, thanks

Next step: merge your ring rework :)

      reply	other threads:[~2017-03-27 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 14:54 Bruce Richardson
2017-03-27 21:58 ` 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=3836698.qL7ye4rpXD@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@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).