From: Shawn Guo <shawnguo@kernel.org>
To: Tim Harvey <tharvey@gateworks.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>
Subject: Re: [PATCH v3] arm64: dts: imx8m{m,n}-venice-*: add missing uart-has-rtscts property to UARTs
Date: Mon, 18 Apr 2022 16:32:01 +0800 [thread overview]
Message-ID: <20220418083201.GG391514@dragon> (raw)
In-Reply-To: <20220411194638.5706-1-tharvey@gateworks.com>
On Mon, Apr 11, 2022 at 12:46:38PM -0700, Tim Harvey wrote:
> Add the missing 'uart-has-rtscts' property to UART's that have hardware
> flow control capability.
>
> Signed-off-by: Tim Harvey <tharvey@gateworks.com>
Applied, thanks!
prev parent reply other threads:[~2022-04-18 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 19:46 [PATCH v3] arm64: dts: imx8m{m,n}-venice-*: add missing uart-has-rtscts property to UARTs Tim Harvey
2022-04-18 8:32 ` 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=20220418083201.GG391514@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tharvey@gateworks.com \
/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).