linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pankaj Gupta <pankaj.gupta@nxp.com>,
	gaurav.jain@nxp.com, horia.geanta@nxp.com, V.Sethi@nxp.com,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	iuliana.prodan@nxp.com, linux-crypto@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [PATCH v4 0/2] caam: init-clk based on caam-page0-access
Date: Mon, 29 Apr 2024 09:19:09 +0200	[thread overview]
Message-ID: <9d217722-3cb7-436c-b445-17e6a3d7cd11@kernel.org> (raw)
In-Reply-To: <20240429062855.923595-1-pankaj.gupta@nxp.com>

On 29/04/2024 08:28, Pankaj Gupta wrote:
> v4:
>  - Correct the null pointer checking
> 
> v3:
>  - Splitting the patch into two.
>  - Disposed-off comments received on v2.
> 
> v2:
>  - Considering the OPTEE enablement check too, for setting the
>    variable 'reg_access'.
> 
> Pankaj Gupta (2):
>   caam: init-clk based on caam-page0-access
>   drivers: crypto: caam: i.MX8ULP donot have CAAM page0 access
> 

Two patches here, 5 patches in patchset, some with entirely different
patch prefixes.

Bring some order to this.

Best regards,
Krzysztof


  parent reply	other threads:[~2024-04-29  7:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29  6:28 [PATCH v4 0/2] caam: init-clk based on caam-page0-access Pankaj Gupta
2024-04-29  6:28 ` Pankaj Gupta
2024-04-29  6:28 ` [PATCH v4 1/2] " Pankaj Gupta
2024-04-29  6:28 ` Pankaj Gupta
2024-04-29  6:28 ` [PATCH v4 2/2] drivers: crypto: caam: i.MX8ULP donot have CAAM page0 access Pankaj Gupta
2024-04-29  6:28 ` Pankaj Gupta
2024-04-29  7:19 ` Krzysztof Kozlowski [this message]
2024-05-10  9:18 ` [PATCH v4 0/2] caam: init-clk based on caam-page0-access 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=9d217722-3cb7-436c-b445-17e6a3d7cd11@kernel.org \
    --to=krzk@kernel.org \
    --cc=V.Sethi@nxp.com \
    --cc=davem@davemloft.net \
    --cc=gaurav.jain@nxp.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@nxp.com \
    --cc=iuliana.prodan@nxp.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pankaj.gupta@nxp.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).