From: Linus Walleij <linus.walleij@linaro.org>
To: Lee Jones <lee.jones@linaro.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Linus WALLEIJ <linus.walleij@stericsson.com>,
Srinidhi KASAGAR <srinidhi.kasagar@stericsson.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH 5/6] crypto: ux500/cryp - Enable DT probing of the driver
Date: Fri, 24 May 2013 08:20:38 +0200 [thread overview]
Message-ID: <CACRpkdZHT0g_Agtug6jC3rU+DYKOpmwqZ9eQAkRGRw5Kj0wW4A@mail.gmail.com> (raw)
In-Reply-To: <1368703646-26418-6-git-send-email-lee.jones@linaro.org>
On Thu, May 16, 2013 at 1:27 PM, Lee Jones <lee.jones@linaro.org> wrote:
> By providing an OF match table with a suitable compatible string, we
> can ensure the ux500-crypt driver is probed by supplying an associated
> DT node in a given platform's Device Tree.
>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: linux-crypto@vger.kernel.org
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
Herbert, can I have your ACK on patch 5 & 6 in this series to take it
through the ARM SoC tree?
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: Lee Jones <lee.jones@linaro.org>,
Herbert Xu <herbert@gondor.hengli.com.au>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Linus WALLEIJ <linus.walleij@stericsson.com>,
Srinidhi KASAGAR <srinidhi.kasagar@stericsson.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH 5/6] crypto: ux500/cryp - Enable DT probing of the driver
Date: Fri, 24 May 2013 08:20:38 +0200 [thread overview]
Message-ID: <CACRpkdZHT0g_Agtug6jC3rU+DYKOpmwqZ9eQAkRGRw5Kj0wW4A@mail.gmail.com> (raw)
In-Reply-To: <1368703646-26418-6-git-send-email-lee.jones@linaro.org>
On Thu, May 16, 2013 at 1:27 PM, Lee Jones <lee.jones@linaro.org> wrote:
> By providing an OF match table with a suitable compatible string, we
> can ensure the ux500-crypt driver is probed by supplying an associated
> DT node in a given platform's Device Tree.
>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: linux-crypto@vger.kernel.org
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
Herbert, can I have your ACK on patch 5 & 6 in this series to take it
through the ARM SoC tree?
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/6] crypto: ux500/cryp - Enable DT probing of the driver
Date: Fri, 24 May 2013 08:20:38 +0200 [thread overview]
Message-ID: <CACRpkdZHT0g_Agtug6jC3rU+DYKOpmwqZ9eQAkRGRw5Kj0wW4A@mail.gmail.com> (raw)
In-Reply-To: <1368703646-26418-6-git-send-email-lee.jones@linaro.org>
On Thu, May 16, 2013 at 1:27 PM, Lee Jones <lee.jones@linaro.org> wrote:
> By providing an OF match table with a suitable compatible string, we
> can ensure the ux500-crypt driver is probed by supplying an associated
> DT node in a given platform's Device Tree.
>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: linux-crypto at vger.kernel.org
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
Herbert, can I have your ACK on patch 5 & 6 in this series to take it
through the ARM SoC tree?
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-05-24 6:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 11:27 [PATCH 0/6] crypto: ux500/[cryp|hash] - Enable Device Tree Lee Jones
2013-05-16 11:27 ` Lee Jones
2013-05-16 11:27 ` [PATCH 1/6] ARM: ux500: Add Device Tree nodes for the ux500 Crypt device Lee Jones
2013-05-16 11:27 ` Lee Jones
2013-05-16 11:27 ` [PATCH 2/6] ARM: ux500: Add Device Tree nodes for the ux500 Hash device Lee Jones
2013-05-16 11:27 ` Lee Jones
2013-05-16 11:27 ` [PATCH 3/6] ARM: ux500: Provide an AUXDATA entry for ux500-cyrpt Lee Jones
2013-05-16 11:27 ` Lee Jones
2013-05-16 11:27 ` [PATCH 4/6] ARM: ux500: Provide an AUXDATA entry for ux500-hash Lee Jones
2013-05-16 11:27 ` Lee Jones
2013-05-16 11:27 ` [PATCH 5/6] crypto: ux500/cryp - Enable DT probing of the driver Lee Jones
2013-05-16 11:27 ` Lee Jones
2013-05-16 11:27 ` Lee Jones
2013-05-24 6:20 ` Linus Walleij [this message]
2013-05-24 6:20 ` Linus Walleij
2013-05-24 6:20 ` Linus Walleij
2013-05-24 6:21 ` Herbert Xu
2013-05-24 6:21 ` Herbert Xu
2013-05-24 6:21 ` Herbert Xu
2013-05-24 8:32 ` Lee Jones
2013-05-24 8:32 ` Lee Jones
2013-05-24 8:32 ` Lee Jones
2013-05-24 11:16 ` Linus Walleij
2013-05-24 11:16 ` Linus Walleij
2013-05-24 11:16 ` Linus Walleij
2013-05-24 6:26 ` Linus Walleij
2013-05-24 6:26 ` Linus Walleij
2013-05-24 6:26 ` Linus Walleij
2013-05-16 11:27 ` [PATCH 6/6] crypto: ux500/hash " Lee Jones
2013-05-16 11:27 ` Lee Jones
2013-05-16 11:27 ` Lee Jones
2013-05-24 6:27 ` [PATCH 0/6] crypto: ux500/[cryp|hash] - Enable Device Tree Linus Walleij
2013-05-24 6:27 ` Linus Walleij
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=CACRpkdZHT0g_Agtug6jC3rU+DYKOpmwqZ9eQAkRGRw5Kj0wW4A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=arnd@arndb.de \
--cc=herbert@gondor.apana.org.au \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinidhi.kasagar@stericsson.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.