devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: fugang.duan@nxp.com
Cc: robh@kernel.org, mark.rutland@arm.com, s.hauer@pengutronix.de,
	shawnguo@kernel.org, kernel@pengutronix.de,
	gregkh@linuxfoundation.org, festevam@gmail.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH nvmem v2 0/2] nvmem: imx: add i.MX8QM platform support
Date: Sun, 18 Aug 2019 10:34:44 +0100	[thread overview]
Message-ID: <5c7e5ff3-f453-c765-8795-c392434c7663@linaro.org> (raw)
In-Reply-To: <20190807040320.1760-1-fugang.duan@nxp.com>



On 07/08/2019 05:03, fugang.duan@nxp.com wrote:
> From: Fugang Duan <fugang.duan@nxp.com>
> 
> The patch set is to add i.MX8QM platform support for i.MX8 SCU
> OCOTP driver due to i.MX8QM efuse table has some difference with
> i.MX8QXP platform.
> 
> V2:
> - Add dt-bindings for the new compatible string support.
> 
> Fugang Duan (2):
>    nvmem: imx: add i.MX8QM platform support
>    dt-bindings: fsl: scu: add new compatible string for ocotp
> 

Applied thanks.

--srini
>   Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt | 4 +++-
>   drivers/nvmem/imx-ocotp-scu.c                               | 7 +++++++
>   2 files changed, 10 insertions(+), 1 deletion(-)
> 

      parent reply	other threads:[~2019-08-18  9:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  4:03 [PATCH nvmem v2 0/2] nvmem: imx: add i.MX8QM platform support fugang.duan
2019-08-07  4:03 ` [PATCH nvmem v2 1/2] " fugang.duan
2019-08-07  4:03 ` [PATCH nvmem v2 2/2] dt-bindings: fsl: scu: add new compatible string for ocotp fugang.duan
2019-08-18  9:34 ` Srinivas Kandagatla [this message]

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=5c7e5ff3-f453-c765-8795-c392434c7663@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=fugang.duan@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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).