All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Warren <tomcwarren3959@gmail.com>
To: Tom Rini <trini@konsulko.com>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Cc: Tom Warren <twarren@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>
Subject: Pull request, u-boot-tegra/master
Date: Fri, 15 Oct 2021 12:50:17 -0700	[thread overview]
Message-ID: <CACih+8W+1TcPiQPS+gobr4n_=3CPQM3d-GFUdA-nV0jbOtXk8A@mail.gmail.com> (raw)

 Tom,

Please pull u-boot-tegra/master into U-Boot/master. Thanks.

The following changes since commit 10cd8efe1a7eacd63907ba95bd8442bc2cdce461:

  Merge branch '2021-10-12-assorted-fixes-and-updates' (2021-10-13 10:14:35
-0400)

are available in the git repository at:

  https://source.denx.de/u-boot/custodians/u-boot-tegra.git master

for you to fetch changes up to a0ba216ed420a8953f57f777256f310370b95338:

  ARM: tegra: Copy memory-region-names property (2021-10-13 14:18:30 -0700)

----------------------------------------------------------------
Thierry Reding (9):
      fdtdec: Allow using fdtdec_get_carveout() in loops
      fdtdec: Support retrieving the name of a carveout
      fdtdec: Support compatible string list for reserved memory
      fdtdec: Reorder fdtdec_set_carveout() parameters for consistency
      fdtdec: Support reserved-memory flags
      ARM: tegra: Support multiple reserved memory regions
      ARM: tegra: Support EMC frequency tables on Tegra210
      ARM: tegra: Refactor DT update helpers
      ARM: tegra: Copy memory-region-names property

 arch/arm/cpu/armv8/fsl-layerscape/soc.c |   3 +-
 arch/arm/include/asm/arch-tegra/board.h |  10 +++
 arch/arm/mach-tegra/dt-setup.c          | 147
++++++++++++++++++++++++++++++++
 arch/riscv/lib/fdt_fixup.c              |   2 +-
 board/nvidia/p2371-2180/p2371-2180.c    |  94 ++------------------
 board/nvidia/p2771-0000/p2771-0000.c    |  98 ++-------------------
 board/nvidia/p3450-0000/p3450-0000.c    |  96 ++-------------------
 include/configs/tegra210-common.h       |   2 +-
 include/fdtdec.h                        |  39 ++++++---
 lib/fdtdec.c                            |  99 ++++++++++++++++++---
 lib/fdtdec_test.c                       |   7 +-
 lib/optee/optee.c                       |   4 +-
 test/dm/fdtdec.c                        |  28 +++---
 13 files changed, 321 insertions(+), 308 deletions(-)

             reply	other threads:[~2021-10-15 19:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 19:50 Tom Warren [this message]
2021-10-18  1:13 ` Pull request, u-boot-tegra/master Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2023-06-05 20:52 Tom Warren
2023-06-05 21:36 ` Tom Rini
2023-02-23 21:25 Tom Warren
2023-02-24 14:43 ` Tom Rini
2023-02-02 17:43 Tom Warren
2023-02-02 19:18 ` Tom Rini
2022-06-14 16:05 Tom Warren
2022-06-14 17:24 ` Tom Rini
2022-06-14 17:56   ` Tom Rini
2021-08-16 23:26 Tom Warren
2021-08-17 13:40 ` Tom Rini
2020-12-04 22:47 Tom Warren
2020-12-07 15:46 ` Tom Rini
2020-06-19 15:53 Tom Warren
2020-06-19 18:21 ` Tom Rini
2020-04-03 17:23 Tom Warren
2020-04-05 23:04 ` Tom Rini
2020-01-14 17:48 Tom Warren
2020-01-15  2:49 ` Tom Rini

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='CACih+8W+1TcPiQPS+gobr4n_=3CPQM3d-GFUdA-nV0jbOtXk8A@mail.gmail.com' \
    --to=tomcwarren3959@gmail.com \
    --cc=thierry.reding@gmail.com \
    --cc=trini@konsulko.com \
    --cc=twarren@nvidia.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.