public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Grant Likely <grant.likely@linaro.org>,
	Stephen Warren <SWarren@nvidia.com>,
	devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rob Herring <rob.herring@calxeda.com>
Subject: Re: [GIT PULL] devicetree bugfixes for v3.10
Date: Thu, 13 Jun 2013 16:56:07 -0600	[thread overview]
Message-ID: <51BA4E07.7060001@wwwdotorg.org> (raw)
In-Reply-To: <1371163963.5555.25.camel@pasglop>

On 06/13/2013 04:52 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2013-06-13 at 23:22 +0100, Grant Likely wrote:
>> Grant Likely (2):
>>       dtc: Update generated files to output from Bison 2.5
>>       dtc: ensure #line directives don't consume data from the next 
> 
> Question. Are those fixes also in the upstream dtc from jdl ? Or have we
> effectively forked it ?

Patch 1 just edits generated files which don't exist upstream (the
kernel checks them in, but upstream relies on the user running Bison/...
as part of make).

Patch 2 is a cherry-pick from upstream (plus regenerating some
difference generated files)

  reply	other threads:[~2013-06-13 22:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 22:22 [GIT PULL] devicetree bugfixes for v3.10 Grant Likely
2013-06-13 22:52 ` Benjamin Herrenschmidt
2013-06-13 22:56   ` Stephen Warren [this message]
2013-06-13 23:42   ` Grant Likely

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=51BA4E07.7060001@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=SWarren@nvidia.com \
    --cc=benh@kernel.crashing.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=torvalds@linux-foundation.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