From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Marcelo Cerri <mhcerri@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 0/2] drivers/crypto/nx: fixes when input data is too large
Date: Thu, 01 Aug 2013 19:26:24 +1000 [thread overview]
Message-ID: <1375349184.3743.73.camel@pasglop> (raw)
In-Reply-To: <1374858488-24658-1-git-send-email-mhcerri@linux.vnet.ibm.com>
On Fri, 2013-07-26 at 14:08 -0300, Marcelo Cerri wrote:
> This series of patches fixes two bugs that are triggered when the input data is
> too large. The first one is caused by the miscalculation of physical addresses
> and the second one by some limits that the co-processor has to the input data.
BTW. Are these supposed to go upstream via my tree or via crypto ?
They are not part of my latest pull request to Linus because they were
not CC'ed to linuxppc-dev so I didn't see them while collecting patches
from patchwork.
If you intend to have them go via the crypto tree that's fine, but if
you intend to have them go via powerpc, then please resend with the
correct mailing list on CC.
Cheers,
Ben.
> Marcelo Cerri (2):
> drivers/crypto/nx: fix physical addresses added to sg lists
> drivers/crypto/nx: fix limits to sg lists for SHA-2
>
> drivers/crypto/nx/nx-sha256.c | 108 +++++++++++++++++++++++-----------------
> drivers/crypto/nx/nx-sha512.c | 113 ++++++++++++++++++++++++------------------
> drivers/crypto/nx/nx.c | 22 ++++++--
> 3 files changed, 148 insertions(+), 95 deletions(-)
>
prev parent reply other threads:[~2013-08-01 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 17:08 [PATCH 0/2] drivers/crypto/nx: fixes when input data is too large Marcelo Cerri
2013-07-26 17:08 ` [PATCH 1/2] drivers/crypto/nx: fix physical addresses added to sg lists Marcelo Cerri
2013-07-26 17:08 ` [PATCH 2/2] drivers/crypto/nx: fix limits to sg lists for SHA-2 Marcelo Cerri
2013-07-26 22:29 ` Benjamin Herrenschmidt
2013-07-29 15:24 ` Marcelo Cerri
2013-07-26 22:31 ` Benjamin Herrenschmidt
2013-07-29 15:19 ` Marcelo Cerri
2013-08-01 9:26 ` Benjamin Herrenschmidt [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=1375349184.3743.73.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhcerri@linux.vnet.ibm.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).