linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Tero Kristo <t-kristo@ti.com>, Suman Anna <s-anna@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Add HwSpinlock & Mailbox nodes on J7200 SoCs
Date: Tue, 17 Nov 2020 06:53:46 -0600	[thread overview]
Message-ID: <160561756333.22964.1029119444913341855.b4-ty@ti.com> (raw)
In-Reply-To: <20201026232637.15681-1-s-anna@ti.com>

On Mon, 26 Oct 2020 18:26:34 -0500, Suman Anna wrote:
> The following series adds the HwSpinlock and Mailbox nodes for the J7200
> series. The sub-mailbox nodes that will be used by the K3 R5F remoteproc
> nodes are also added to the k3-j7200-som-p0.dtsi file in sync with the
> convention used on J721E SoCs.
> 
> Patches are based on 5.10-rc1 and your current staged branch commit
> 9dcd17be61e4 ("arm64: dts: ti: k3-am65: ringacc: drop
> ti,dma-ring-reset-quirk")
> 
> [...]

Hi Suman Anna,

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

[1/3] arm64: dts: ti: k3-j7200-main: Add hwspinlock node
      commit: 1d7a01c40840d844fb5d353c151f0ee0a7680c2f
[2/3] arm64: dts: ti: k3-j7200-main: Add mailbox cluster nodes
      commit: d15d1cfbd765b4b2a113b6025e8edc7db4a7800a
[3/3] arm64: dts: ti: k3-j7200-som-p0: Add IPC sub-mailbox nodes
      commit: 6804a987de733c805675973e3afde128fe7a7cfa


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


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2020-11-17 12:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 23:26 [PATCH 0/3] Add HwSpinlock & Mailbox nodes on J7200 SoCs Suman Anna
2020-10-26 23:26 ` [PATCH 1/3] arm64: dts: ti: k3-j7200-main: Add hwspinlock node Suman Anna
2020-10-26 23:26 ` [PATCH 2/3] arm64: dts: ti: k3-j7200-main: Add mailbox cluster nodes Suman Anna
2020-10-26 23:26 ` [PATCH 3/3] arm64: dts: ti: k3-j7200-som-p0: Add IPC sub-mailbox nodes Suman Anna
2020-10-27 12:41 ` [PATCH 0/3] Add HwSpinlock & Mailbox nodes on J7200 SoCs Nishanth Menon
2020-11-16 16:46   ` Bajjuri, Praneeth
2020-11-17 12:53 ` 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=160561756333.22964.1029119444913341855.b4-ty@ti.com \
    --to=nm@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=s-anna@ti.com \
    --cc=t-kristo@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;
as well as URLs for NNTP newsgroup(s).