From: Linus Walleij <linus.walleij@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-crypto@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Joakim Bech <joakim.bech@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 5/5] dt-bindings: add Atmel SHA204A I2C crypto processor
Date: Thu, 9 May 2019 22:44:51 +0200 [thread overview]
Message-ID: <CACRpkdYGzOCAecgG=MkFRJyVEK9sfSXHq7g959TzDvXNWqA-Ug@mail.gmail.com> (raw)
In-Reply-To: <20190430162910.16771-6-ard.biesheuvel@linaro.org>
On Tue, Apr 30, 2019 at 6:29 PM Ard Biesheuvel
<ard.biesheuvel@linaro.org> wrote:
> Add a compatible string for the Atmel SHA204A I2C crypto processor.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-05-09 20:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 16:29 [PATCH 0/5] synquacer - wire up Atmel SHA204A as RNG in DT and ACPI mode Ard Biesheuvel
2019-04-30 16:29 ` [PATCH 1/5] i2c: acpi: permit bus speed to be discovered after enumeration Ard Biesheuvel
2019-05-02 8:08 ` Mika Westerberg
2019-04-30 16:29 ` [PATCH 2/5] crypto: atmel-ecc: add support for ACPI probing on non-AT91 platforms Ard Biesheuvel
2019-04-30 16:29 ` [PATCH 3/5] crypto: atmel-ecc: factor out code that can be shared Ard Biesheuvel
2019-05-09 20:42 ` Linus Walleij
2019-04-30 16:29 ` [PATCH 4/5] crypto: atmel-i2c: add support for SHA204A random number generator Ard Biesheuvel
2019-05-09 20:44 ` Linus Walleij
2019-04-30 16:29 ` [PATCH 5/5] dt-bindings: add Atmel SHA204A I2C crypto processor Ard Biesheuvel
2019-05-09 20:44 ` Linus Walleij [this message]
2019-05-16 16:06 ` Ard Biesheuvel
2019-05-24 13:12 ` Rob Herring
2019-05-24 13:15 ` Ard Biesheuvel
2019-05-24 13:36 ` Rob Herring
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='CACRpkdYGzOCAecgG=MkFRJyVEK9sfSXHq7g959TzDvXNWqA-Ug@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=joakim.bech@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mark.rutland@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).