public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Kim Phillips <kim.phillips@freescale.com>
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: Tue, 26 Feb 2013 21:08:06 -0600	[thread overview]
Message-ID: <1361934486.18483.5@driftwood> (raw)
In-Reply-To: <1361928975-29395-2-git-send-email-kim.phillips@freescale.com> (from kim.phillips@freescale.com on Tue Feb 26 19:36:14 2013)

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?

> "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.

Ummm... huh?

Rob

  reply	other threads:[~2013-02-27  3:08 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 [this message]
2013-02-27 16:45     ` Kim Phillips
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=1361934486.18483.5@driftwood \
    --to=rob@landley.net \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=kim.phillips@freescale.com \
    --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 \
    /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