From: Kyle Yan <kyan@codeaurora.org>
To: robh@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Makefile in libfdt shows non-existent files
Date: Fri, 14 Jul 2017 17:52:47 -0700 [thread overview]
Message-ID: <f81acd4a-3ed5-02aa-5e0a-0d625c2c7566@codeaurora.org> (raw)
Hi Rob,
I was trying the latest dtc as on Linux 4.12 for device tree overlay. On
the latest kernel, I see the following commit:
commit 6f05afcbb031722ec1eff77dde188ff2edf8940e ("scripts/dtc: Update to
upstream version 0931cea3ba20")
This seems to pull in various upstream dtc commits for dtc overlay
including:
commit 0cdd06c5135bd9f46853c2f58ad2ac91b0fa87f3 ("libfdt: Add overlay
application function")
The upstream commit introduces libfdt/fdt_overlay.c, but this file is
not reflected in the kernel. Similar case is also seen for
libfdt/fdt_addresses.c.
Can you help confirm if these files should indeed have been pulled into
the kernel and if anything else is missing from DTC side.
Thanks,
Kyle
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2017-07-15 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 0:52 Kyle Yan [this message]
2017-07-15 1:19 ` 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=f81acd4a-3ed5-02aa-5e0a-0d625c2c7566@codeaurora.org \
--to=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
all inboxes | Powered by JetHome®