From: Conor Dooley <conor@kernel.org>
To: Komal Bajaj <quic_kbajaj@quicinc.com>
Cc: agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
srinivas.kandagatla@linaro.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support
Date: Mon, 24 Jul 2023 17:54:22 +0100 [thread overview]
Message-ID: <20230724-paternity-labrador-e8f4046b3398@spud> (raw)
In-Reply-To: <20230724-shabby-schnapps-e7254584400c@spud>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
On Mon, Jul 24, 2023 at 05:53:36PM +0100, Conor Dooley wrote:
> On Mon, Jul 24, 2023 at 02:08:47PM +0530, Komal Bajaj wrote:
> > Changes in v5 -
> > - Separating this from original series [1].
> > - Added description of driver to secure qfprom binding.
> > - Replaced pm_runtime_enable() withh devm_pm_runtime_enable().
> > - Changed module license to GPL instead of GPL v2.
> >
> > This series introduces a new driver for reading secure fuse region and adding
> > dt-bindings for same.
> >
> > [1] https://lore.kernel.org/linux-arm-msm/20230623141806.13388-1-quic_kbajaj@quicinc.com/
>
> Why does this series have two v5s?
Never mind, I missed the reply Komal. Apologies!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-07-24 16:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:38 [PATCH v5 0/2] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support Komal Bajaj
2023-07-24 8:38 ` [PATCH v5 1/2] dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom Komal Bajaj
2023-07-26 16:40 ` Rob Herring
2023-07-28 13:54 ` Komal Bajaj
2023-07-27 9:09 ` Pavan Kondeti
2023-07-28 13:57 ` Komal Bajaj
2023-07-24 8:38 ` [PATCH v5 2/2] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support Komal Bajaj
2023-07-26 6:17 ` Bjorn Andersson
2023-07-27 6:39 ` Mukesh Ojha
2023-07-27 13:26 ` Mukesh Ojha
2023-07-31 16:35 ` Bjorn Andersson
2023-08-01 6:10 ` Komal Bajaj
2023-07-27 10:44 ` Srinivas Kandagatla
2023-07-28 8:25 ` Mukesh Ojha
2023-08-01 6:11 ` Komal Bajaj
2023-07-24 8:40 ` [PATCH v5 0/2] " Komal Bajaj
2023-07-24 16:53 ` Conor Dooley
2023-07-24 16:54 ` Conor Dooley [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-24 8:29 Komal Bajaj
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=20230724-paternity-labrador-e8f4046b3398@spud \
--to=conor@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kbajaj@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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).