From: Kim Phillips <kim.phillips@freescale.com>
To: Martin Hicks <mort@bork.org>
Cc: "Scott Wood" <scottwood@freescale.com>,
linuxppc-dev@lists.ozlabs.org,
"Horia Geantă" <horia.geanta@freescale.com>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v2 2/5] crypto: talitos: Remove MD5_BLOCK_SIZE
Date: Thu, 5 Mar 2015 18:07:26 -0600 [thread overview]
Message-ID: <20150305180726.6ab76042f99af0eb62b64ed6@freescale.com> (raw)
In-Reply-To: <1425388897-5434-3-git-send-email-mort@bork.org>
On Tue, 3 Mar 2015 08:21:34 -0500
Martin Hicks <mort@bork.org> wrote:
> This is properly defined in the md5 header file.
>
> Signed-off-by: Martin Hicks <mort@bork.org>
> ---
Acked-by: Kim Phillips <kim.phillips@freescale.com>
Kim
next prev parent reply other threads:[~2015-03-06 0:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 13:21 [PATCH v2 0/5] crypto: talitos: Add crypto async queue handling Martin Hicks
2015-03-03 13:21 ` [PATCH v2 1/5] crypto: talitos: Simplify per-channel initialization Martin Hicks
2015-03-06 0:06 ` Kim Phillips
2015-03-03 13:21 ` [PATCH v2 2/5] crypto: talitos: Remove MD5_BLOCK_SIZE Martin Hicks
2015-03-06 0:07 ` Kim Phillips [this message]
2015-03-06 12:02 ` Herbert Xu
2015-03-03 13:21 ` [PATCH v2 3/5] crypto: talitos: Fix off-by-one and use all hardware slots Martin Hicks
2015-03-04 0:35 ` Kim Phillips
2015-03-04 14:46 ` Martin Hicks
2015-03-03 13:21 ` [PATCH v2 4/5] crypto: talitos: Reorganize request submission data structures Martin Hicks
2015-03-03 13:21 ` [PATCH v2 5/5] crypto: talitos: Add software backlog queue handling Martin Hicks
2015-03-04 0:23 ` Kim Phillips
2015-03-05 9:35 ` Horia Geantă
2015-03-06 0:34 ` Kim Phillips
2015-03-06 4:48 ` Herbert Xu
2015-03-09 12:08 ` Horia Geantă
2015-03-16 10:02 ` Horia Geantă
2015-03-17 0:19 ` Kim Phillips
2015-03-17 17:58 ` Horia Geantă
2015-03-17 22:03 ` Kim Phillips
2015-03-19 15:56 ` Horia Geantă
2015-03-19 18:38 ` Kim Phillips
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=20150305180726.6ab76042f99af0eb62b64ed6@freescale.com \
--to=kim.phillips@freescale.com \
--cc=horia.geanta@freescale.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mort@bork.org \
--cc=scottwood@freescale.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).