linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Eric Biggers <ebiggers@google.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: Make extension enablement consistent
Date: Wed, 25 Mar 2020 17:00:58 +0100	[thread overview]
Message-ID: <CAMj1kXGGTvn0r_jLuUxXJmuO+nvV0o_K=kZ++csZJ1Z6rU+a+g@mail.gmail.com> (raw)
In-Reply-To: <20200325135522.7782-1-broonie@kernel.org>

On Wed, 25 Mar 2020 at 14:55, Mark Brown <broonie@kernel.org> wrote:
>
> Currently we use a mix of .arch and .cpu to enable architecture
> extensions, make things consistent by converting the two instances of
> .cpu to .arch which is more common and a bit more idiomatic for our
> goal.
>
> Mark Brown (2):
>   arm64: crypto: Consistently enable extension
>   arm64: lib: Consistently enable crc32 extension
>

Acked-by: Ard Biesheuvel <ardb@kernel.org>

>  arch/arm64/crypto/crct10dif-ce-core.S | 2 +-
>  arch/arm64/lib/crc32.S                | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> --
> 2.20.1
>

      parent reply	other threads:[~2020-03-25 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 13:55 Mark Brown
2020-03-25 13:55 ` [PATCH 1/2] arm64: crypto: Consistently enable extension Mark Brown
2020-03-25 13:55 ` [PATCH 2/2] arm64: lib: Consistently enable crc32 extension Mark Brown
2020-03-25 16:00 ` Ard Biesheuvel [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='CAMj1kXGGTvn0r_jLuUxXJmuO+nvV0o_K=kZ++csZJ1Z6rU+a+g@mail.gmail.com' \
    --to=ardb@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=ebiggers@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=will@kernel.org \
    --subject='Re: [PATCH 0/2] arm64: Make extension enablement consistent' \
    /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

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).