From: Vignesh Raghavendra <vigneshr@ti.com>
To: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Bryan Brattlof <bb@ti.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] arm64: dts: ti: Add support for AM62A family of SoCs
Date: Mon, 19 Sep 2022 21:33:36 +0530 [thread overview]
Message-ID: <166360336860.225542.16586137913783585865.b4-ty@ti.com> (raw)
In-Reply-To: <20220901141328.899100-1-vigneshr@ti.com>
Hi Vignesh Raghavendra,
On Thu, 1 Sep 2022 19:43:23 +0530, Vignesh Raghavendra wrote:
> This series adds basic boot support for AM62A SoCs with UART, MMC/SD and
> GPIO support on AM62A SK EVM
>
> Bootlog: https://gist.github.com/r-vignesh/4d88f53bb0489f1675fa78f993e95d3f
> Tech Ref manual: https://www.ti.com/lit/zip/spruj16
> Schematics: https://www.ti.com/lit/zip/sprr459
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/5] dt-bindings: arm: ti: Rearrange IOPAD macros alphabetically
commit: a3c52977419beabc5cb4d6f0b062fd4cb460e54d
[2/5] dt-bindings: arm: ti: Add bindings for AM62A7 SoC
commit: cad20a8de86f37d2500963b1a424f9d658d8e54a
[3/5] dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM62A
commit: 1607e6f9289cdb4c982a223e80ff3c5e827b7cd4
[4/5] arm64: dts: ti: Introduce AM62A7 family of SoCs
commit: 5fc6b1b62639c764e6e7e261f384d2fb47eff39b
[5/5] arm64: dts: ti: Add support for AM62A7-SK
commit: 38c4a08c820cd2483750a68f2bf84c3665fe6137
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh
_______________________________________________
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:[~2022-09-19 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 14:13 [PATCH v2 0/5] arm64: dts: ti: Add support for AM62A family of SoCs Vignesh Raghavendra
2022-09-01 14:13 ` [PATCH v2 1/5] dt-bindings: arm: ti: Rearrange IOPAD macros alphabetically Vignesh Raghavendra
2022-09-07 20:40 ` Rob Herring
2022-09-01 14:13 ` [PATCH v2 2/5] dt-bindings: arm: ti: Add bindings for AM62A7 SoC Vignesh Raghavendra
2022-09-07 20:41 ` Rob Herring
2022-09-01 14:13 ` [PATCH v2 3/5] dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM62A Vignesh Raghavendra
2022-09-01 14:13 ` [PATCH v2 4/5] arm64: dts: ti: Introduce AM62A7 family of SoCs Vignesh Raghavendra
2022-09-01 14:13 ` [PATCH v2 5/5] arm64: dts: ti: Add support for AM62A7-SK Vignesh Raghavendra
2022-09-13 6:57 ` [PATCH v2 0/5] arm64: dts: ti: Add support for AM62A family of SoCs Devarsh Thakkar
2022-09-19 16:03 ` Vignesh Raghavendra [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=166360336860.225542.16586137913783585865.b4-ty@ti.com \
--to=vigneshr@ti.com \
--cc=bb@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@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).