All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"samitolvanen@google.com" <samitolvanen@google.com>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH v2] crypto/arm: accelerated SHA-512 using ARM generic ASM and NEON
Date: Mon, 13 Apr 2015 11:34:51 +0200	[thread overview]
Message-ID: <CAKv+Gu_7RAAvWRpfAvTCs3zNPvbfrD=V7AHcJr+Qcj0B9Sf9TA@mail.gmail.com> (raw)
In-Reply-To: <20150413041343.GB11091@gondor.apana.org.au>

On 13 April 2015 at 06:13, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Sat, Apr 11, 2015 at 09:15:10PM +0200, Ard Biesheuvel wrote:
>>
>> @Herbert: could you please apply this onto cryptodev before sending
>> out your pull request for v4.1?
>
> Done.
>
>> And please disregard $subject, I will post a v3 with a similar
>> 'depends on' added (unless you're ok to add it yourself)
>
> Please resend the patch.  But I'll process it after the merge
> window closes so no hurry.
>


OK, all fine.

Thanks Herbert!

WARNING: multiple messages have this Message-ID (diff)
From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] crypto/arm: accelerated SHA-512 using ARM generic ASM and NEON
Date: Mon, 13 Apr 2015 11:34:51 +0200	[thread overview]
Message-ID: <CAKv+Gu_7RAAvWRpfAvTCs3zNPvbfrD=V7AHcJr+Qcj0B9Sf9TA@mail.gmail.com> (raw)
In-Reply-To: <20150413041343.GB11091@gondor.apana.org.au>

On 13 April 2015 at 06:13, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Sat, Apr 11, 2015 at 09:15:10PM +0200, Ard Biesheuvel wrote:
>>
>> @Herbert: could you please apply this onto cryptodev before sending
>> out your pull request for v4.1?
>
> Done.
>
>> And please disregard $subject, I will post a v3 with a similar
>> 'depends on' added (unless you're ok to add it yourself)
>
> Please resend the patch.  But I'll process it after the merge
> window closes so no hurry.
>


OK, all fine.

Thanks Herbert!

  reply	other threads:[~2015-04-13  9:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 14:29 [PATCH v2] crypto/arm: accelerated SHA-512 using ARM generic ASM and NEON Ard Biesheuvel
2015-04-10 14:29 ` Ard Biesheuvel
2015-04-10 20:08 ` Arnd Bergmann
2015-04-10 20:08   ` Arnd Bergmann
2015-04-10 20:23   ` Ard Biesheuvel
2015-04-10 20:23     ` Ard Biesheuvel
2015-04-11  7:35     ` Ard Biesheuvel
2015-04-11  7:35       ` Ard Biesheuvel
2015-04-11  8:48       ` Arnd Bergmann
2015-04-11  8:48         ` Arnd Bergmann
2015-04-11 10:27         ` Ard Biesheuvel
2015-04-11 10:27           ` Ard Biesheuvel
2015-04-11 20:43           ` Arnd Bergmann
2015-04-11 20:43             ` Arnd Bergmann
2015-04-11 19:15         ` Ard Biesheuvel
2015-04-11 19:15           ` Ard Biesheuvel
2015-04-13  4:13           ` Herbert Xu
2015-04-13  4:13             ` Herbert Xu
2015-04-13  9:34             ` Ard Biesheuvel [this message]
2015-04-13  9:34               ` Ard Biesheuvel

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='CAKv+Gu_7RAAvWRpfAvTCs3zNPvbfrD=V7AHcJr+Qcj0B9Sf9TA@mail.gmail.com' \
    --to=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=samitolvanen@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.