From: Viresh Kumar <viresh.kumar@linaro.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Frank Rowand <frowand.list@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Masahiro Yamada <masahiroy@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Bill Mills <bill.mills@linaro.org>,
anmar.oueja@linaro.org
Subject: Re: [PATCH V5 3/5] scripts: dtc: Remove the unused fdtdump.c file
Date: Thu, 21 Jan 2021 09:47:57 +0530 [thread overview]
Message-ID: <20210121041757.cskxlai5e7a2pfgb@vireshk-i7> (raw)
In-Reply-To: <20210121004457.GD5174@yekko.fritz.box>
On 21-01-21, 11:44, David Gibson wrote:
> On Wed, Jan 20, 2021 at 12:36:45PM +0530, Viresh Kumar wrote:
> > This was copied from external DTC repository long back and isn't used
> > anymore. Over that the dtc tool can be used to generate the dts source
> > back from the dtb. Remove the unused fdtdump.c file.
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> Doesn't this make updating the kernel dtc from upstream needlessly
> more difficult?
Hmm, I am not sure I understand the concern well. The kernel keeps a
list of files[1] it needs to automatically copy (using a script) from
the upstream dtc repo and fdtdump.c was never part of that. Keeping it
there isn't going to make any difficulty I believe.
--
viresh
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scripts/dtc/update-dtc-source.sh
next prev parent reply other threads:[~2021-01-21 4:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 7:06 [PATCH V5 0/5] dt: build overlays Viresh Kumar
2021-01-20 7:06 ` [PATCH V5 1/5] scripts: dtc: Fetch fdtoverlay.c from external DTC project Viresh Kumar
2021-01-20 7:06 ` [PATCH V5 2/5] scripts: dtc: Build fdtoverlay tool Viresh Kumar
2021-01-20 7:06 ` [PATCH V5 3/5] scripts: dtc: Remove the unused fdtdump.c file Viresh Kumar
2021-01-21 0:44 ` David Gibson
2021-01-21 4:17 ` Viresh Kumar [this message]
2021-01-21 6:26 ` David Gibson
2021-01-21 14:18 ` Rob Herring
2021-01-20 7:06 ` [PATCH V5 4/5] kbuild: Add support to build overlays (%.dtbo) Viresh Kumar
2021-01-20 8:58 ` Masahiro Yamada
2021-01-20 9:55 ` Viresh Kumar
2021-01-20 11:04 ` Masahiro Yamada
2021-01-20 11:27 ` Viresh Kumar
2021-01-21 0:49 ` David Gibson
2021-01-21 4:13 ` Viresh Kumar
2021-01-21 5:40 ` Frank Rowand
2021-01-21 6:25 ` David Gibson
2021-01-20 7:06 ` [PATCH V5 5/5] of: unittest: Statically apply overlays using fdtoverlay Viresh Kumar
2021-01-21 0:51 ` David Gibson
2021-01-21 5:14 ` Frank Rowand
2021-01-21 5:34 ` Viresh Kumar
2021-01-21 5:45 ` Frank Rowand
2021-01-21 5:50 ` Viresh Kumar
2021-01-21 6:36 ` David Gibson
2021-01-21 6:34 ` David Gibson
2021-01-21 6:57 ` Viresh Kumar
2021-01-21 23:39 ` David Gibson
2021-01-22 3:10 ` Viresh Kumar
2021-01-22 4:27 ` David Gibson
2021-01-21 5:34 ` Frank Rowand
2021-01-21 5:43 ` Viresh Kumar
2021-01-21 5:55 ` Frank Rowand
2021-01-21 5:58 ` Viresh Kumar
2021-01-21 7:04 ` Frank Rowand
2021-01-21 23:41 ` David Gibson
2021-01-21 6:37 ` David Gibson
2021-01-20 15:43 ` [PATCH V5 0/5] dt: build overlays Rob Herring
2021-01-21 4:14 ` Viresh Kumar
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=20210121041757.cskxlai5e7a2pfgb@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=anmar.oueja@linaro.org \
--cc=bill.mills@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.org \
--cc=vincent.guittot@linaro.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).