All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: Etienne Carriere <etienne.carriere@st.com>,
	devicetree@vger.kernel.org, alexandre.torgue@st.com,
	linux-kernel@vger.kernel.org, robh+dt@kernel.org,
	srinivas.kandagatla@linaro.org, mcoquelin.stm32@gmail.com,
	fabrice.gasnier@st.com, linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: nvmem: stm32: new property for data access
Date: Mon, 11 May 2020 20:35:19 -0500	[thread overview]
Message-ID: <20200512013519.GA2002@bogus> (raw)
In-Reply-To: <20200508134527.26555-1-etienne.carriere@linaro.org>

On Fri,  8 May 2020 15:45:27 +0200, Etienne Carriere wrote:
> From: Etienne Carriere <etienne.carriere@st.com>
> 
> Introduce boolean property st,non-secure-otp for OTP data located
> in a factory programmed area that only secure firmware can access
> by default and that shall be reachable from the non-secure world.
> 
> Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
> ---
>  .../bindings/nvmem/st,stm32-romem.yaml          | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 

Applied, thanks!

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

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, fabrice.gasnier@st.com,
	linux-stm32@st-md-mailman.stormreply.com,
	mcoquelin.stm32@gmail.com, alexandre.torgue@st.com,
	srinivas.kandagatla@linaro.org,
	Etienne Carriere <etienne.carriere@st.com>
Subject: Re: [PATCH] dt-bindings: nvmem: stm32: new property for data access
Date: Mon, 11 May 2020 20:35:19 -0500	[thread overview]
Message-ID: <20200512013519.GA2002@bogus> (raw)
In-Reply-To: <20200508134527.26555-1-etienne.carriere@linaro.org>

On Fri,  8 May 2020 15:45:27 +0200, Etienne Carriere wrote:
> From: Etienne Carriere <etienne.carriere@st.com>
> 
> Introduce boolean property st,non-secure-otp for OTP data located
> in a factory programmed area that only secure firmware can access
> by default and that shall be reachable from the non-secure world.
> 
> Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
> ---
>  .../bindings/nvmem/st,stm32-romem.yaml          | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 

Applied, thanks!

  reply	other threads:[~2020-05-12  1:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 13:45 [PATCH] dt-bindings: nvmem: stm32: new property for data access Etienne Carriere
2020-05-08 13:45 ` Etienne Carriere
2020-05-12  1:35 ` Rob Herring [this message]
2020-05-12  1:35   ` Rob Herring
2020-05-12  1:51 ` Rob Herring
2020-05-12  1:51   ` Rob Herring
2020-05-12  9:58   ` Etienne Carriere
2020-05-12  9:58     ` Etienne Carriere

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=20200512013519.GA2002@bogus \
    --to=robh@kernel.org \
    --cc=alexandre.torgue@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=etienne.carriere@linaro.org \
    --cc=etienne.carriere@st.com \
    --cc=fabrice.gasnier@st.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.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 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.