devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Rob Herring <robh@kernel.org>, <davem@davemloft.net>,
	Keerthy <j-keerthy@ti.com>, <devicetree@vger.kernel.org>,
	<linux-crypto@vger.kernel.org>
Subject: Re: [PATCHv3 1/7] dt-bindings: crypto: Add TI SA2UL crypto accelerator documentation
Date: Wed, 3 Jun 2020 15:38:03 +0300	[thread overview]
Message-ID: <18c28e88-e3a7-2ec4-1d0c-f4d4163aff1c@ti.com> (raw)
In-Reply-To: <20200603122726.GB31719@gondor.apana.org.au>

On 03/06/2020 15:27, Herbert Xu wrote:
> On Wed, Jun 03, 2020 at 01:01:26PM +0300, Tero Kristo wrote:
>>
>> Herbert, whats the plan with the rest of the series? Do you want me to
>> re-post it? It shows deferred under crypto patchwork currently.
> 
> Please repost because v3 contains just a single patch.

Also I guess this should be posted against 5.8-rc1 once it is out, as 
merge window is already open. Or are you planning to pick it up for 5.8 
already?

-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

  reply	other threads:[~2020-06-03 12:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200424164430.3288-1-t-kristo@ti.com>
2020-04-24 16:44 ` [PATCHv2 1/7] dt-bindings: crypto: Add TI SA2UL crypto accelerator documentation Tero Kristo
2020-05-11 21:53   ` Rob Herring
2020-05-12  4:47     ` Tero Kristo
2020-05-14 12:50     ` [PATCHv3 " Tero Kristo
2020-05-26 13:16       ` Tero Kristo
2020-05-28 15:23       ` Rob Herring
2020-06-03 10:01         ` Tero Kristo
2020-06-03 12:27           ` Herbert Xu
2020-06-03 12:38             ` Tero Kristo [this message]
2020-06-03 12:39               ` Herbert Xu
2020-06-03 12:53                 ` Tero Kristo
2020-06-03 12:54                   ` 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=18c28e88-e3a7-2ec4-1d0c-f4d4163aff1c@ti.com \
    --to=t-kristo@ti.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=j-keerthy@ti.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=robh@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).