From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
yaeceh01 <yael.chemla@foss.arm.com>,
Ofir Drang <Ofir.Drang@arm.com>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] dt-bindings: crypto: ccree: add dt bindings for ccree 703
Date: Tue, 4 Dec 2018 10:38:26 +0200 [thread overview]
Message-ID: <CAOtvUMepGR89J-5SQXnReRiHanrOhp52cEKKm58Ej2uoHFAcyA@mail.gmail.com> (raw)
In-Reply-To: <20181129064218.53qc33vus5anla76@gondor.apana.org.au>
On Thu, Nov 29, 2018 at 8:42 AM Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> On Tue, Nov 13, 2018 at 09:40:36AM +0000, Gilad Ben-Yossef wrote:
> > Add device tree bindings associating Arm TrustZone CryptoCell 703 with the
> > ccree driver.
> >
> > Signed-off-by: Gilad Ben-Yossef <gilad@benyossef.com>
> > ---
> > Documentation/devicetree/bindings/crypto/arm-cryptocell.txt | 1 +
> > 1 file changed, 1 insertion(+)
>
> Which tree is this patch meant to go through?
I'm not sure the question was addressed to me but if it did - either
going through the device tree or the crypto tree is fine by me.
Thanks,
Gilad
next prev parent reply other threads:[~2018-12-04 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 9:40 [PATCH 0/3] new HW version and co-maintainer Gilad Ben-Yossef
2018-11-13 9:40 ` [PATCH 1/3] crypto: ccree: add support for CryptoCell 703 Gilad Ben-Yossef
2018-11-13 9:40 ` [PATCH 2/3] dt-bindings: crypto: ccree: add dt bindings for ccree 703 Gilad Ben-Yossef
2018-11-29 6:42 ` Herbert Xu
2018-12-04 8:38 ` Gilad Ben-Yossef [this message]
2018-12-04 20:14 ` Rob Herring
2018-12-05 1:40 ` Herbert Xu
2018-12-04 20:14 ` Rob Herring
2018-11-13 9:40 ` [PATCH 3/3] MAINTAINERS: ccree: add co-maintainer Gilad Ben-Yossef
2018-12-07 6:18 ` [PATCH 0/3] new HW version and co-maintainer Herbert Xu
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=CAOtvUMepGR89J-5SQXnReRiHanrOhp52cEKKm58Ej2uoHFAcyA@mail.gmail.com \
--to=gilad@benyossef.com \
--cc=Ofir.Drang@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=yael.chemla@foss.arm.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 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).