From: Neil Armstrong <narmstrong@baylibre.com>
To: Vyacheslav Bocharov <adeep@lexina.in>,
Kevin Hilman <khilman@baylibre.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/3] arm64: meson: update dts for JetHub devices
Date: Fri, 25 Mar 2022 18:34:02 +0100 [thread overview]
Message-ID: <394573e1-0786-75ef-65fa-4b75d57714f2@baylibre.com> (raw)
In-Reply-To: <20220325165501.81551-1-adeep@lexina.in>
Hi,
On 25/03/2022 17:54, Vyacheslav Bocharov wrote:
> Update dts for JetHub H1:
> - add bluetooth node for RTL8822CS uart port
>
> Update dts for JetHub D1:
> - add ZigBee serial alias (ttyAML2) for backward compatibility
> - update voltage regulators and SDIO config to match board's reference design
>
> Vyacheslav Bocharov (3):
> arm64: meson: add to dts for JetHub H1 bluetooth node
> arm64: meson: dts: update dts for JetHub D1
> arm64: meson: fix sdio in dts for JetHub D1
>
> .../amlogic/meson-axg-jethome-jethub-j100.dts | 17 +++++++++++++----
> .../meson-gxl-s905w-jethome-jethub-j80.dts | 5 +++++
> 2 files changed, 18 insertions(+), 4 deletions(-)
>
Can you add Fixes: tag in all patches so they get backported ?
Thanks,
Neil
next prev parent reply other threads:[~2022-03-25 19:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 16:54 [PATCH 0/3] arm64: meson: update dts for JetHub devices Vyacheslav Bocharov
2022-03-25 16:54 ` [PATCH 1/3] arm64: meson: add dts bluetooth node for JetHub H1 Vyacheslav Bocharov
2022-03-25 17:32 ` Neil Armstrong
2022-03-25 16:55 ` [PATCH 2/3] arm64: meson: dts: update serial alias in dts for JetHub D1 Vyacheslav Bocharov
2022-03-25 16:55 ` [PATCH 3/3] arm64: meson: update SDIO " Vyacheslav Bocharov
2022-03-25 17:33 ` Neil Armstrong
2022-03-25 17:34 ` Neil Armstrong [this message]
2022-03-26 7:42 ` [PATCH 0/3] arm64: meson: update dts for JetHub devices Vyacheslav
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=394573e1-0786-75ef-65fa-4b75d57714f2@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=adeep@lexina.in \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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).