devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] scripts/dtc: dtx_diff: remove broken example from help text
Date: Thu, 13 Jan 2022 11:09:40 -0600	[thread overview]
Message-ID: <23ae99a0-a91f-8259-15c2-f9cf051f5ed8@gmail.com> (raw)
In-Reply-To: <20220113081918.10387-1-matthias.schiffer@ew.tq-group.com>

On 1/13/22 2:19 AM, Matthias Schiffer wrote:
> dtx_diff suggests to use <(...) syntax to pipe two inputs into it, but
> this has never worked: The /proc/self/fds/... paths passed by the shell
> will fail the `[ -f "${dtx}" ] && [ -r "${dtx}" ]` check in compile_to_dts,
> but even with this check removed, the function cannot work: hexdump will
> eat up the DTB magic, making the subsequent dtc call fail, as a pipe
> cannot be rewound.
> 
> Simply remove this broken example, as there is already an alternative one
> that works fine.
> 
> Fixes: 10eadc253ddf ("dtc: create tool to diff device trees")
> Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
> ---
>  scripts/dtc/dtx_diff | 8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
> 
> diff --git a/scripts/dtc/dtx_diff b/scripts/dtc/dtx_diff
> index d3422ee15e30..f2bbde4bba86 100755
> --- a/scripts/dtc/dtx_diff
> +++ b/scripts/dtc/dtx_diff
> @@ -59,12 +59,8 @@ Otherwise DTx is treated as a dts source file (aka .dts).
>     or '/include/' to be processed.
>  
>     If DTx_1 and DTx_2 are in different architectures, then this script
> -   may not work since \${ARCH} is part of the include path.  Two possible
> -   workarounds:
> -
> -      `basename $0` \\
> -          <(ARCH=arch_of_dtx_1 `basename $0` DTx_1) \\
> -          <(ARCH=arch_of_dtx_2 `basename $0` DTx_2)
> +   may not work since \${ARCH} is part of the include path.  The following
> +   workaround can be used:
>  
>        `basename $0` ARCH=arch_of_dtx_1 DTx_1 >tmp_dtx_1.dts
>        `basename $0` ARCH=arch_of_dtx_2 DTx_2 >tmp_dtx_2.dts
>
Reviewed-by: Frank Rowand <frank.rowand@sony.com>

  reply	other threads:[~2022-01-13 17:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  8:19 [PATCH v2] scripts/dtc: dtx_diff: remove broken example from help text Matthias Schiffer
2022-01-13 17:09 ` Frank Rowand [this message]
2022-01-14 15:26 ` Rob Herring

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=23ae99a0-a91f-8259-15c2-f9cf051f5ed8@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.schiffer@ew.tq-group.com \
    --cc=robh+dt@kernel.org \
    /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).