All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Abel Vesa <abel.vesa@nxp.com>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	linux-arm-kernel@lists.infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 1/3] dt-bindings: fsl: scu: Add i.MX8QM rtc binding
Date: Wed, 22 Dec 2021 14:29:40 -0400	[thread overview]
Message-ID: <YcNulKqtIg8Unm76@robh.at.kernel.org> (raw)
In-Reply-To: <1640088948-3690-2-git-send-email-abel.vesa@nxp.com>

On Tue, 21 Dec 2021 14:15:46 +0200, Abel Vesa wrote:
> Add i.MX8QM rtc compatible to the SCU bindings documentation.
> 
> Signed-off-by: Abel Vesa <abel.vesa@nxp.com>
> ---
>  Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 

Acked-by: Rob Herring <robh@kernel.org>

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Abel Vesa <abel.vesa@nxp.com>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	linux-arm-kernel@lists.infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 1/3] dt-bindings: fsl: scu: Add i.MX8QM rtc binding
Date: Wed, 22 Dec 2021 14:29:40 -0400	[thread overview]
Message-ID: <YcNulKqtIg8Unm76@robh.at.kernel.org> (raw)
In-Reply-To: <1640088948-3690-2-git-send-email-abel.vesa@nxp.com>

On Tue, 21 Dec 2021 14:15:46 +0200, Abel Vesa wrote:
> Add i.MX8QM rtc compatible to the SCU bindings documentation.
> 
> Signed-off-by: Abel Vesa <abel.vesa@nxp.com>
> ---
>  Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 

Acked-by: Rob Herring <robh@kernel.org>

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

  reply	other threads:[~2021-12-22 18:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 12:15 [PATCH 0/3] Add RTC support to i.MX8QM Abel Vesa
2021-12-21 12:15 ` Abel Vesa
2021-12-21 12:15 ` [PATCH 1/3] dt-bindings: fsl: scu: Add i.MX8QM rtc binding Abel Vesa
2021-12-21 12:15   ` Abel Vesa
2021-12-22 18:29   ` Rob Herring [this message]
2021-12-22 18:29     ` Rob Herring
2021-12-29 21:36   ` Alexandre Belloni
2021-12-29 21:36     ` Alexandre Belloni
2022-01-03 19:46     ` Abel Vesa
2022-01-03 19:46       ` Abel Vesa
2021-12-21 12:15 ` [PATCH 2/3] rtc: imx-sc: Add i.MX8QM RTC support Abel Vesa
2021-12-21 12:15   ` Abel Vesa
2021-12-21 12:15 ` [PATCH 3/3] arm64: dts: imx8qm: Add SCU RTC node Abel Vesa
2021-12-21 12:15   ` Abel Vesa

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=YcNulKqtIg8Unm76@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=abel.vesa@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.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 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.