From: Shawn Guo <shawnguo@kernel.org>
To: Alistair Francis <alistair@alistair23.me>
Cc: devicetree@vger.kernel.org, s.hauer@pengutronix.de,
krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
linux-imx@nxp.com, linux@armlinux.org.uk, arnd@arndb.de,
alistair23@gmail.com, kernel@pengutronix.de, festevam@gmail.com,
jernej.skrabec@gmail.com
Subject: Re: [PATCH v4 0/3] imx7d-remarkable2: Enable cyttsp5 and rohm,bd71815
Date: Tue, 14 Mar 2023 11:01:14 +0800 [thread overview]
Message-ID: <20230314030114.GK143566@dragon> (raw)
In-Reply-To: <20230227045023.560319-1-alistair@alistair23.me>
On Mon, Feb 27, 2023 at 02:50:20PM +1000, Alistair Francis wrote:
> Enable the cyttsp5 and rohm,bd71815 in the device trees and
> defconfig for the reMarkable 2.
>
> v4:
> - Fixup the rohm changes to match DT schema
> v3:
> - Remove unused sleep states
> v2:
> - Fixup DT formatting issues in path 3
>
> Alistair Francis (3):
> ARM: dts: imx7d-remarkable2: Enable the cyttsp5
> ARM: imx_v6_v7_defconfig: Enable rohm,bd71815
> ARM: dts: imx7d-remarkable2: Enable the rohm,bd71815
Applied all, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-14 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 4:50 [PATCH v4 0/3] imx7d-remarkable2: Enable cyttsp5 and rohm,bd71815 Alistair Francis
2023-02-27 4:50 ` [PATCH v4 1/3] ARM: dts: imx7d-remarkable2: Enable the cyttsp5 Alistair Francis
2023-02-27 4:50 ` [PATCH v4 2/3] ARM: imx_v6_v7_defconfig: Enable rohm,bd71815 Alistair Francis
2023-02-27 4:50 ` [PATCH v4 3/3] ARM: dts: imx7d-remarkable2: Enable the rohm,bd71815 Alistair Francis
2023-03-14 3:01 ` 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=20230314030114.GK143566@dragon \
--to=shawnguo@kernel.org \
--cc=alistair23@gmail.com \
--cc=alistair@alistair23.me \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jernej.skrabec@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=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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).