From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 resend 0/5] arm64: advertise availability of CRC and crypto instructions
Date: Thu, 23 Jan 2014 15:01:23 +0000 [thread overview]
Message-ID: <20140123150123.GH27520@arm.com> (raw)
In-Reply-To: <1389950591-4212-1-git-send-email-ard.biesheuvel@linaro.org>
On Fri, Jan 17, 2014 at 09:23:06AM +0000, Ard Biesheuvel wrote:
> Ard Biesheuvel (5):
> ARM: add support for AT_HWCAP2 ELF auxv entry
> binfmt_elf: add ELF_HWCAP2 to compat auxv entries
> arm64: add AT_HWCAP2 support for 32-bit compat
> ARM: introduce HWCAP2 feature bits for ARMv8 Crypto Extensions
> arm64: advertise ARMv8 extensions to 32-bit compat ELF binaries
I think I acked this series but probably after you posted the resend.
Just in case I haven't:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2014-01-23 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 9:23 [PATCH v2 resend 0/5] arm64: advertise availability of CRC and crypto instructions Ard Biesheuvel
2014-01-17 9:23 ` [PATCH v2 resend 1/5] ARM: add support for AT_HWCAP2 ELF auxv entry Ard Biesheuvel
2014-01-17 15:07 ` Will Deacon
2014-01-17 15:26 ` Ard Biesheuvel
2014-01-17 9:23 ` [PATCH v2 resend 2/5] binfmt_elf: add ELF_HWCAP2 to compat auxv entries Ard Biesheuvel
2014-01-17 9:23 ` [PATCH v2 resend 3/5] arm64: add AT_HWCAP2 support for 32-bit compat Ard Biesheuvel
2014-01-17 9:23 ` [PATCH v2 resend 4/5] ARM: introduce HWCAP2 feature bits for ARMv8 Crypto Extensions Ard Biesheuvel
2014-01-17 9:23 ` [PATCH v2 resend 5/5] arm64: advertise ARMv8 extensions to 32-bit compat ELF binaries Ard Biesheuvel
2014-01-23 15:01 ` Catalin Marinas [this message]
2014-02-05 13:37 ` [PATCH v2 resend 0/5] arm64: advertise availability of CRC and crypto instructions Catalin Marinas
2014-02-19 21:40 ` 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=20140123150123.GH27520@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).