Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Markus Schneider-Pargmann <msp@baylibre.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Vishal Mahaveer <vishalm@ti.com>,
	Kevin Hilman <khilman@baylibre.com>, Dhruva Gole <d-gole@ti.com>,
	Sebin Francis <sebin.francis@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] arm64: dts: ti: k3-am62*-sk: Add wkup/mcu_uart0 aliases
Date: Mon, 3 Mar 2025 10:19:55 +0530	[thread overview]
Message-ID: <174092143358.3272913.5963413997044284059.b4-ty@ti.com> (raw)
In-Reply-To: <20250203-topic-am62-serial-aliases-v6-14-v1-0-f26d4124a9f1@baylibre.com>

Hi Markus Schneider-Pargmann,

On Mon, 03 Feb 2025 10:34:09 +0100, Markus Schneider-Pargmann wrote:
> add serial aliases for wkup and mcu uart0. Add them to have the same
> order on all boards as well.
> 
> Best
> Markus
> 
> 
> [...]

I have applied the following to branch ti-next on [1].
Thank you!

[1/3] arm64: dts: ti: k3-am62x-sk-common: Add serial aliases
      commit: 3e7f622685e8c3ae3adb5d905f56008c4371c660
[2/3] arm64: dts: ti: k3-am62a7-sk: Add serial alias
      commit: 5a74aef8821885e3d567f4a67bc20ecd723731e7
[3/3] arm64: dts: ti: k3-am62p5-sk: Add serial alias
      commit: 8b0f601f9869b01e2dc35c5860eb0f8ce0650be5

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



      parent reply	other threads:[~2025-03-03  4:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03  9:34 [PATCH 0/3] arm64: dts: ti: k3-am62*-sk: Add wkup/mcu_uart0 aliases Markus Schneider-Pargmann
2025-02-03  9:34 ` [PATCH 1/3] arm64: dts: ti: k3-am62x-sk-common: Add serial aliases Markus Schneider-Pargmann
2025-02-04  3:53   ` Nishanth Menon
2025-02-07 12:58     ` Markus Schneider-Pargmann
2025-02-03  9:34 ` [PATCH 2/3] arm64: dts: ti: k3-am62a7-sk: Add serial alias Markus Schneider-Pargmann
2025-02-03  9:34 ` [PATCH 3/3] arm64: dts: ti: k3-am62p5-sk: " Markus Schneider-Pargmann
2025-03-03  4:49 ` 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=174092143358.3272913.5963413997044284059.b4-ty@ti.com \
    --to=vigneshr@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=d-gole@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msp@baylibre.com \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=sebin.francis@ti.com \
    --cc=vishalm@ti.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