devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] Various TQMa6UL/MBa6ULx fixes
Date: Sun, 24 Sep 2023 21:23:09 +0800	[thread overview]
Message-ID: <20230924132309.GH7231@dragon> (raw)
In-Reply-To: <20230816075452.606704-1-alexander.stein@ew.tq-group.com>

On Wed, Aug 16, 2023 at 09:54:50AM +0200, Alexander Stein wrote:
> Hi,
> this is a follow up to v1 for fixing dtbs_check warnings for TQMa6UL/MBa6ULx.
> While Patch 1 & 3 from v1 have been applied, Patch 2 is inserted into this v2
> again. The patch itself is not changed, because a dependent patch was missing
> in v1. This one has been included in v2.
> 
> Changes in v2:
> * Add a missing dependent patch as new patch 1
> 
> Best regards,
> Alexander
> 
> Alexander Stein (2):
>   ARM: dts: imx6ul: mba6ulx: Mark gpio-buttons as wakeup-source
>   ARM: dts: imx6ul: mba6ulx: Fix gpio-keys button node names

Applied both, thanks!

      parent reply	other threads:[~2023-09-24 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  7:54 [PATCH v2 0/2] Various TQMa6UL/MBa6ULx fixes Alexander Stein
2023-08-16  7:54 ` [PATCH v2 1/2] ARM: dts: imx6ul: mba6ulx: Mark gpio-buttons as wakeup-source Alexander Stein
2023-08-16  7:54 ` [PATCH v2 2/2] ARM: dts: imx6ul: mba6ulx: Fix gpio-keys button node names Alexander Stein
2023-09-24 13:23 ` Shawn Guo [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=20230924132309.GH7231@dragon \
    --to=shawnguo@kernel.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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).