All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
	robh+dt@kernel.org, wens@csie.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-sunxi@googlegroups.com, m.cerveny@computer.org
Subject: Re: [PATCH v3] dt-bindings: crypto: Specify that allwinner,sun8i-a33-crypto needs reset
Date: Tue, 8 Sep 2020 08:19:49 +0200	[thread overview]
Message-ID: <20200908061949.ff7swgzv72lb6jd3@gilmour.lan> (raw)
In-Reply-To: <20200908061556.btaokh5ftxng7t7m@gilmour.lan>

[-- Attachment #1: Type: text/plain, Size: 646 bytes --]

On Tue, Sep 08, 2020 at 08:15:56AM +0200, Maxime Ripard wrote:
> On Mon, Sep 07, 2020 at 07:54:37PM +0200, Corentin Labbe wrote:
> > When adding allwinner,sun8i-a33-crypto, I forgot to add that it needs reset.
> > Furthermore, there are no need to use items to list only one compatible
> > in compatible list.
> > 
> > Fixes: f81547ba7a98 ("dt-bindings: crypto: add new compatible for A33 SS")
> > Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>
> 
> Acked-by: Maxime Ripard <mripard@kernel.org>

Nevermind, I assumed that there would be crypto patches, but there's
none so I ended up taking it through our tree.

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime@cerno.tech>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: devicetree@vger.kernel.org, herbert@gondor.apana.org.au,
	linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org,
	wens@csie.org, robh+dt@kernel.org, linux-crypto@vger.kernel.org,
	m.cerveny@computer.org, davem@davemloft.net,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] dt-bindings: crypto: Specify that allwinner,sun8i-a33-crypto needs reset
Date: Tue, 8 Sep 2020 08:19:49 +0200	[thread overview]
Message-ID: <20200908061949.ff7swgzv72lb6jd3@gilmour.lan> (raw)
In-Reply-To: <20200908061556.btaokh5ftxng7t7m@gilmour.lan>


[-- Attachment #1.1: Type: text/plain, Size: 646 bytes --]

On Tue, Sep 08, 2020 at 08:15:56AM +0200, Maxime Ripard wrote:
> On Mon, Sep 07, 2020 at 07:54:37PM +0200, Corentin Labbe wrote:
> > When adding allwinner,sun8i-a33-crypto, I forgot to add that it needs reset.
> > Furthermore, there are no need to use items to list only one compatible
> > in compatible list.
> > 
> > Fixes: f81547ba7a98 ("dt-bindings: crypto: add new compatible for A33 SS")
> > Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>
> 
> Acked-by: Maxime Ripard <mripard@kernel.org>

Nevermind, I assumed that there would be crypto patches, but there's
none so I ended up taking it through our tree.

Maxime

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-09-08  6:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07 17:54 [PATCH v3] dt-bindings: crypto: Specify that allwinner,sun8i-a33-crypto needs reset Corentin Labbe
2020-09-07 17:54 ` [PATCH v3] dt-bindings: crypto: Specify that allwinner, sun8i-a33-crypto " Corentin Labbe
2020-09-08  6:15 ` [PATCH v3] dt-bindings: crypto: Specify that allwinner,sun8i-a33-crypto " Maxime Ripard
2020-09-08  6:15   ` Maxime Ripard
2020-09-08  6:19   ` Maxime Ripard [this message]
2020-09-08  6:19     ` Maxime Ripard

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=20200908061949.ff7swgzv72lb6jd3@gilmour.lan \
    --to=maxime@cerno.tech \
    --cc=clabbe.montjoie@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=m.cerveny@computer.org \
    --cc=robh+dt@kernel.org \
    --cc=wens@csie.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 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.