From: Kim Phillips <kim.phillips@freescale.com>
To: Rob Landley <rob@landley.net>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Russell King <linux@arm.linux.org.uk>,
Nicolas Pitre <nico@linaro.org>,
<devicetree-discuss@lists.ozlabs.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] dtc: import latest upstream dtc
Date: Wed, 27 Feb 2013 10:45:12 -0600 [thread overview]
Message-ID: <20130227104512.c07c0ade0107aa7f4ec18217@freescale.com> (raw)
In-Reply-To: <1361934486.18483.5@driftwood>
On Tue, 26 Feb 2013 21:08:06 -0600
Rob Landley <rob@landley.net> wrote:
> On 02/26/2013 07:36:14 PM, Kim Phillips wrote:
> > This updates scripts/dtc to upstream dtc commit 27cdc1b
>
> There's an upstream for dts?
dtc - the device tree compiler, yes.
> > "Added license header to dtc/libfdt/fdt.h and libfdt_env.h"
> > from git://git.jdl.com/software/dtc.git.
>
> That git repository has a Documentation directory with for example
> "dts-format.txt" in it. My current linux git repository does not
> contain a file called dts-format.txt.
this patch isn't attempting to update dts-format.txt, or any other
file that exists in the upstream dtc project that isn't present -
and used - in the kernel. The purpose of this patch is to update
libfdt, which has in-kernel users.
Kim
next prev parent reply other threads:[~2013-02-27 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 1:36 [PATCH 1/3] libfdt: add fdt type definitions in libfdt_env.h Kim Phillips
2013-02-27 1:36 ` [PATCH 2/3] dtc: import latest upstream dtc Kim Phillips
2013-02-27 3:08 ` Rob Landley
2013-02-27 16:45 ` Kim Phillips [this message]
2013-02-27 1:36 ` [PATCH 3/3] ARM: zImage: sparse fixes Kim Phillips
2013-02-27 17:05 ` [PATCH 1/3] libfdt: add fdt type definitions in libfdt_env.h 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=20130227104512.c07c0ade0107aa7f4ec18217@freescale.com \
--to=kim.phillips@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@linaro.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
/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®