linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	Tero Kristo <kristo@kernel.org>,
	Lokesh Vutla <lokeshvutla@ti.com>,
	Rob Herring <robh+dt@kernel.org>, Suman Anna <s-anna@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] AM64: Update the locations of various elements in SRAM
Date: Wed, 16 Jun 2021 19:11:08 -0500	[thread overview]
Message-ID: <162388856677.17633.14731996075089826400.b4-ty@ti.com> (raw)
In-Reply-To: <20210616171224.24635-1-a-govindraju@ti.com>

On Wed, 16 Jun 2021 22:42:21 +0530, Aswath Govindraju wrote:
> The following series of patches,
> - Increase the maximum size of TF-A
> - Update the location of TF-A due to a limitation for DFU boot
> - Indicate reserved locations for DMSC code and secure proxy
> 
> 
> Link to corresponding U-Boot series that makes these changes:
> - https://patchwork.ozlabs.org/project/uboot/list/?series=249235
> 
> [...]

Hi Aswath Govindraju,

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


NOTE: I updated the $subject of patch #3 to be:
arm64: dts: ti: k3-am64-main: Update TF-A load address to workaround USB DFU
limitation

[1/3] arm64: dts: ti: k3-am64-main: Update TF-A's maximum size and node name
      commit: 263820efa3fb08cc606736b68290d9be9c46e2e5
[2/3] arm64: dts: ti: k3-am64-main: Reserve OCMRAM for DMSC-lite and secure proxy communication
      commit: 454a9d4aaacb89daea350d21628992bb83de649f
[3/3] arm64: dts: ti: k3-am64-main: Update TF-A load address to workaround USB DFU limitation
      commit: 3de27ef12ccb50205e602d92f29d082429aa2964


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-06-17  0:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 17:12 [PATCH v5 0/3] AM64: Update the locations of various elements in SRAM Aswath Govindraju
2021-06-16 17:12 ` [PATCH v5 1/3] arm64: dts: ti: k3-am64-main: Update TF-A's maximum size and node name Aswath Govindraju
2021-06-16 17:16   ` Suman Anna
2021-06-16 17:12 ` [PATCH v5 2/3] arm64: dts: ti: k3-am64-main: Reserve OCMRAM for DMSC-lite and secure proxy communication Aswath Govindraju
2021-06-16 17:12 ` [PATCH v5 3/3] arm64: dts: ti: k3-am64-main: Update the location of TF-A in compliance with U-Boot v2021.10 Aswath Govindraju
2021-06-16 17:17   ` Suman Anna
2021-06-17  0:11 ` 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=162388856677.17633.14731996075089826400.b4-ty@ti.com \
    --to=nm@ti.com \
    --cc=a-govindraju@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --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=s-anna@ti.com \
    --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;
as well as URLs for NNTP newsgroup(s).