All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@konsulko.com>,
	 Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	 Jernej Skrabec <jernej.skrabec@gmail.com>,
	Samuel Holland <samuel@sholland.org>,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	Andre Przywara <andre.przywara@arm.com>
Subject: Re: [PATCH 2/3] cmd: fdt: allow standalone "fdt move"
Date: Sun, 17 Jul 2022 04:12:57 -0400	[thread overview]
Message-ID: <CAPnjgZ33r=AX6AiJMTuLkJQjg_PESpQPtcny_BnfnGRPwW1b_w@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ0J1Vbtj-PvUe1w2NZ_CnunZy3ivE6J6p_WxxaMpvV8nw@mail.gmail.com>

On Tue, 5 Jul 2022 at 11:14, Andre Przywara <andre.przywara@arm.com> wrote:
>
> At the moment every subcommand of "fdt", except "addr" itself, requires
> the DT address to be set first. We explicitly check for that before even
> comparing against the subcommands' string.
> This early bailout also affects the "move" subcommand, even though that
> does not require or rely on a previous call to "fdt addr". In fact it
> even sets the FDT address to the target of the move command, so is a
> perfect beginning for a sequence of fdt commands.
>
> Move the check for a previously set FDT address to after we handle the
> "move" command also, so we don't need a dummy call to "fdt addr" first,
> before being able to move the devicetree.
>
> This skips one pointless "fdt addr" call in scripts which aim to alter
> the control DT, but need to copy it to a safe location first (for
> instance to $fdt_addr_r).
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
>  cmd/fdt.c | 28 +++++++++++++++++-----------
>  1 file changed, 17 insertions(+), 11 deletions(-)

Reviewed-by: Simon Glass <sjg@chromium.org>

Applied to u-boot-dm, thanks!

  parent reply	other threads:[~2022-07-17  8:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 17:13 [PATCH 0/3] fdt: introduce "apply-all" command Andre Przywara
2022-07-05 17:13 ` [PATCH 1/3] cmd: fdt: move: Use map_sysmem to convert pointers Andre Przywara
2022-07-12 10:58   ` Simon Glass
2022-07-17  8:12   ` Simon Glass
2022-07-05 17:13 ` [PATCH 2/3] cmd: fdt: allow standalone "fdt move" Andre Przywara
2022-07-12 10:58   ` Simon Glass
2022-07-17  8:12   ` Simon Glass [this message]
2022-07-05 17:13 ` [PATCH 3/3] fdt: introduce apply_all command Andre Przywara
2022-07-12 10:58   ` Simon Glass
2022-07-13 13:17     ` Andre Przywara
2022-07-13 15:45       ` Simon Glass

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='CAPnjgZ33r=AX6AiJMTuLkJQjg_PESpQPtcny_BnfnGRPwW1b_w@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=andre.przywara@arm.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=samuel@sholland.org \
    --cc=trini@konsulko.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.