From: leroy christophe <christophe.leroy@c-s.fr>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-crypto@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 0/17] crypto: talitos - Add support for SEC1
Date: Fri, 06 Mar 2015 07:44:29 +0100 [thread overview]
Message-ID: <54F94CCD.8030807@c-s.fr> (raw)
In-Reply-To: <20150305182101.6db66e228f519476f0751c13@freescale.com>
Le 06/03/2015 01:21, Kim Phillips a écrit :
> 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
It was applying ok on linux-next as of yesterday.
I will rebase the serie on cryptodev-2.6
Christophe
prev parent reply other threads:[~2015-03-06 6:44 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
2015-03-06 0:28 ` Herbert Xu
2015-03-06 8:39 ` leroy christophe
2015-03-06 6:44 ` leroy christophe [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=54F94CCD.8030807@c-s.fr \
--to=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=kim.phillips@freescale.com \
--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;
as well as URLs for NNTP newsgroup(s).