From: Tom Rini <trini@konsulko.com>
To: Rob Herring <robh@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Kyle Yan <kyan@codeaurora.org>
Subject: Re: [PATCH 1/2] scripts/dtc: add fdt_overlay.c and fdt_addresses.c to sync script
Date: Thu, 5 Oct 2017 10:39:30 -0400 [thread overview]
Message-ID: <20171005143930.GB25966@bill-the-cat> (raw)
In-Reply-To: <CAL_Jsq+Ruvu11Nu92FtgGcO0PqxCQk5KhiQAgj8JzbzPKNseqQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]
On Tue, Oct 03, 2017 at 05:23:28PM -0500, Rob Herring wrote:
> On Tue, Oct 3, 2017 at 5:04 PM, Tom Rini <trini@konsulko.com> wrote:
> > On Tue, Oct 03, 2017 at 01:31:17PM -0500, Rob Herring wrote:
> >
> >> libfdt has gained some new files. We need to include them in the
> >> kernel's copy.
> >>
> >> Reported-by: Kyle Yan <kyan@codeaurora.org>
> >> Signed-off-by: Rob Herring <robh@kernel.org>
> >> ---
> >> scripts/dtc/update-dtc-source.sh | 4 +++-
> >> 1 file changed, 3 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/scripts/dtc/update-dtc-source.sh b/scripts/dtc/update-dtc-source.sh
> >> index b8ebcc6722d2..f3e5c596050a 100755
> >> --- a/scripts/dtc/update-dtc-source.sh
> >> +++ b/scripts/dtc/update-dtc-source.sh
> >> @@ -34,7 +34,9 @@ DTC_SOURCE="checks.c data.c dtc.c dtc.h flattree.c fstree.c livetree.c srcpos.c
> >> srcpos.h treesource.c util.c util.h version_gen.h Makefile.dtc \
> >> dtc-lexer.l dtc-parser.y"
> >> DTC_GENERATED="dtc-lexer.lex.c dtc-parser.tab.c dtc-parser.tab.h"
> >> -LIBFDT_SOURCE="Makefile.libfdt fdt.c fdt.h fdt_empty_tree.c fdt_ro.c fdt_rw.c fdt_strerror.c fdt_sw.c fdt_wip.c libfdt.h libfdt_env.h libfdt_internal.h"
> >> +LIBFDT_SOURCE="Makefile.libfdt fdt.c fdt.h fdt_addresses.c fdt_empty_tree.c \
> >> + fdt_overlay.c fdt_ro.c fdt_rw.c fdt_strerror.c fdt_sw.c \
> >> + fdt_wip.c libfdt.h libfdt_env.h libfdt_internal.h"
> >
> > Should there be a patch #3 to update the kernel libfdt to include these
> > new files that we're copying in too? That seems to be the main user
> > in-tree of the libfdt C files, aside from the 'libfdt' targets under
> > arch/{arm,powerpc}/boot/ Thanks!
>
> Yes, good point. But we can add them when someone wants to use them.
> Adding them to the build will bloat the kernel because libfdt doesn't
> get built as a static lib (another problem to solve).
Well, isn't the kernel starting to more widely use
-ffunction-sections/-fdata-sections/--gc-unused-sections ?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-10-05 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 18:31 [PATCH 1/2] scripts/dtc: add fdt_overlay.c and fdt_addresses.c to sync script Rob Herring
2017-10-03 18:31 ` [PATCH 2/2] scripts/dtc: Update to upstream version v1.4.5-3-gb1a60033c110 Rob Herring
[not found] ` <20171003183118.2438-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-10-03 22:04 ` [PATCH 1/2] scripts/dtc: add fdt_overlay.c and fdt_addresses.c to sync script Tom Rini
2017-10-03 22:23 ` Rob Herring
2017-10-05 14:39 ` Tom Rini [this message]
2017-10-05 15:09 ` Rob Herring
[not found] ` <CAL_JsqLGm_OhJUUys7-1s_+rk48sJPKBVR_dTJOB4Lu92GL_Zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-05 19:50 ` 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=20171005143930.GB25966@bill-the-cat \
--to=trini@konsulko.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=kyan@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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