mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>, <kristo@kernel.org>
Cc: Nishanth Menon <nm@ti.com>, <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	Vignesh R <vigneshr@ti.com>,
	Device Tree Mailing List <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] arm64: dts: ti: k3-am64: Add PWM nodes
Date: Fri, 30 Jul 2021 10:46:23 -0500	[thread overview]
Message-ID: <162765993452.9115.3360387735192186820.b4-ty@ti.com> (raw)
In-Reply-To: <20210721113625.17299-1-lokeshvutla@ti.com>

On Wed, 21 Jul 2021 17:06:21 +0530, Lokesh Vutla wrote:
> Add epwm and ecap nodes for AM64 boards.
> 
> Changes since v1:
> - Mark all un-used pwm nodes as disabled.
> 
> Lokesh Vutla (4):
>   arm64: dts: ti: k3-am64-main: Add epwm nodes
>   arm64: dts: ti: k3-am64-main: Add ecap pwm nodes
>   arm64: dts: ti: k3-am642-evm: Add pwm nodes
>   arm64: dts: ti: k3-am642-sk: Add pwm nodes
> 
> [...]

Hi Lokesh Vutla,

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

[1/4] arm64: dts: ti: k3-am64-main: Add epwm nodes
      commit: 13a9a3ef66248a1b6e9acaaa5292d96f8635935b
[2/4] arm64: dts: ti: k3-am64-main: Add ecap pwm nodes
      commit: ae0df139b51a8448afb38e9706f257ab56fea097
[3/4] arm64: dts: ti: k3-am642-evm: Add pwm nodes
      commit: 8032affdf5a156a467d3b109f32cd9f57ea7afda
[4/4] arm64: dts: ti: k3-am642-sk: Add pwm nodes
      commit: c1fa5ac6c2f475b5140e6323801ed93c24e7e5cf


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] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D)/Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D


      parent reply	other threads:[~2021-07-30 15:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 11:36 Lokesh Vutla
2021-07-21 11:36 ` [PATCH v2 1/4] arm64: dts: ti: k3-am64-main: Add epwm nodes Lokesh Vutla
2021-07-21 18:26   ` Grygorii Strashko
2021-07-21 11:36 ` [PATCH v2 2/4] arm64: dts: ti: k3-am64-main: Add ecap pwm nodes Lokesh Vutla
2021-07-21 18:27   ` Grygorii Strashko
2021-07-21 11:36 ` [PATCH v2 3/4] arm64: dts: ti: k3-am642-evm: Add " Lokesh Vutla
2021-07-21 18:27   ` Grygorii Strashko
2021-07-21 11:36 ` [PATCH v2 4/4] arm64: dts: ti: k3-am642-sk: " Lokesh Vutla
2021-07-21 18:27   ` Grygorii Strashko
2021-07-30 15:46 ` Nishanth Menon [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=162765993452.9115.3360387735192186820.b4-ty@ti.com \
    --to=nm@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@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

all inboxes | Powered by JetHome®