From: Fabio Estevam <festevam@gmail.com>
To: Adam Ford <aford173@gmail.com>
Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: Add GPC Support
Date: Sat, 30 Nov 2019 20:01:50 -0300 [thread overview]
Message-ID: <CAOMZO5Czqqe0p1LEWt11S-zXnejg_9Zob5wPf2Df5ZJh2dT0qg@mail.gmail.com> (raw)
In-Reply-To: <CAHCN7x+zJt3i=Yw=2HjdtQa-rR4yMMvCMf319+wgMW0XQ=nF4g@mail.gmail.com>
On Sat, Nov 30, 2019 at 7:50 PM Adam Ford <aford173@gmail.com> wrote:
> I held off intentionally because of all the txt->yaml conversion, I
> didn't want to get stuck in the middle of that.
>
> Would an tweak to the txt file be accepted?
Yes, a patch to the existing txt binding should be fine.
next prev parent reply other threads:[~2019-11-30 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 23:41 [PATCH 1/2] soc: imx: gpcv2: Add support for imx8mm Adam Ford
2019-11-29 23:41 ` [PATCH 2/2] arm64: dts: Add GPC Support Adam Ford
2019-11-30 22:25 ` Fabio Estevam
2019-11-30 22:30 ` Fabio Estevam
2019-11-30 22:49 ` Adam Ford
2019-11-30 23:01 ` Fabio Estevam [this message]
2019-12-02 14:28 ` [PATCH 1/2] soc: imx: gpcv2: Add support for imx8mm Philipp Zabel
2019-12-02 15:17 ` Adam Ford
2019-12-04 3:42 ` Adam Ford
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=CAOMZO5Czqqe0p1LEWt11S-zXnejg_9Zob5wPf2Df5ZJh2dT0qg@mail.gmail.com \
--to=festevam@gmail.com \
--cc=aford173@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).