From: Kim Phillips <kim.phillips@freescale.com>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>, <linux-kernel@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>, <linux-crypto@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 0/17] crypto: talitos - Add support for SEC1
Date: Thu, 5 Mar 2015 18:21:01 -0600 [thread overview]
Message-ID: <20150305182101.6db66e228f519476f0751c13@freescale.com> (raw)
In-Reply-To: <20150305164605.E65D81A241C@localhost.localdomain>
On Thu, 5 Mar 2015 17:46:05 +0100
Christophe Leroy <christophe.leroy@c-s.fr> wrote:
> [15/17] crypto: talitos - Implementation of SEC1
...
> [16/17] crypto: talitos - SEC1 bugs on 0 data hash
> [17/17] crypto: talitos - Update DT bindings with SEC1
This patchseries doesn't apply, at least on top of Herbert's
cryptodev-2.6 tree, as of today:
Applying: crypto: talitos - Implementation of SEC1
error: patch failed: drivers/crypto/talitos.c:655
error: drivers/crypto/talitos.c: patch does not apply
Kim
next prev parent reply other threads:[~2015-03-06 0:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 16:46 [PATCH 0/17] crypto: talitos - Add support for SEC1 Christophe Leroy
2015-03-06 0:21 ` Kim Phillips [this message]
2015-03-06 0:28 ` Herbert Xu
[not found] ` <20150306002831.GA30947-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org>
2015-03-06 8:39 ` leroy christophe
[not found] ` <20150305182101.6db66e228f519476f0751c13-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-03-06 6:44 ` leroy christophe
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=20150305182101.6db66e228f519476f0751c13@freescale.com \
--to=kim.phillips@freescale.com \
--cc=christophe.leroy@c-s.fr \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=herbert@gondor.apana.org.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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