public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ARM: add module autoloading support for crypto modules
Date: Wed, 15 Feb 2017 19:24:25 +0000	[thread overview]
Message-ID: <20170215192425.GD27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CAKv+Gu9DFFM6LEKxs5E9jugfRj4CKHb-5nVoD4uzrjmbvk9rGg@mail.gmail.com>

On Wed, Feb 15, 2017 at 05:16:47PM +0000, Ard Biesheuvel wrote:
> On 31 January 2017 at 13:47, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> > On 19 January 2017 at 18:23, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> >> On 11 January 2017 at 17:01, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> >>> This series wires up the crypto modules that use the ARM 32-bit versions of
> >>> the ARMv8 Crypto Extensions to udev autoloading, by exposing the HWCAP2
> >>> feature bits via the CPU modalias. This is very similar to the arm64
> >>> implementation, with the notable exception that ARM has its CPU feature
> >>> definitions split across HWCAP and HWCAP2.
> >>>
> >>> Given that the crypto feature bits are all exposed via HWCAP2, and considering
> >>> that there are currently no features exposed via HWCAP that are relevant to
> >>> udev module autoloading, exposing HWCAP2 only should be sufficient, at least
> >>> for now.
> >>>
> >>> Changes since v1:
> >>> - rebase onto v4.10-rc2
> >>>
> >>> Ard Biesheuvel (5):
> >>>   ARM: wire up HWCAP2 feature bits to the CPU modalias
> >>
> >> Ping?
> >>
> >
> > Ping?
> 
> Ping?

Sorry, but whom are you pinging?

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2017-02-15 19:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 17:01 [PATCH v2 0/5] ARM: add module autoloading support for crypto modules Ard Biesheuvel
2017-01-11 17:01 ` [PATCH v2 1/5] ARM: wire up HWCAP2 feature bits to the CPU modalias Ard Biesheuvel
2017-01-11 17:01 ` [PATCH v2 2/5] crypto: arm/aes-ce - enable module autoloading based on CPU feature bits Ard Biesheuvel
2017-01-11 17:01 ` [PATCH v2 3/5] crypto: arm/ghash-ce " Ard Biesheuvel
2017-01-11 17:01 ` [PATCH v2 4/5] crypto: arm/sha1-ce " Ard Biesheuvel
2017-01-11 17:01 ` [PATCH v2 5/5] crypto: arm/sha2-ce " Ard Biesheuvel
2017-01-19 18:23 ` [PATCH v2 0/5] ARM: add module autoloading support for crypto modules Ard Biesheuvel
2017-01-31 13:47   ` Ard Biesheuvel
2017-02-15 17:16     ` Ard Biesheuvel
2017-02-15 19:24       ` Russell King - ARM Linux [this message]
2017-02-15 19:29         ` Ard Biesheuvel
2017-02-15 19:35           ` Russell King - ARM Linux
2017-02-15 20:00 ` Russell King - ARM Linux
2017-02-15 20:04   ` Ard Biesheuvel
2017-02-15 20:07     ` Russell King - ARM Linux
2017-02-15 20:38       ` 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=20170215192425.GD27312@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --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