From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Grant Likely <grant.likely@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Rob Herring <rob.herring@calxeda.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
Stephen Warren <SWarren@nvidia.com>
Subject: Re: [GIT PULL] devicetree bugfixes for v3.10
Date: Fri, 14 Jun 2013 08:52:43 +1000 [thread overview]
Message-ID: <1371163963.5555.25.camel@pasglop> (raw)
In-Reply-To: <CACxGe6sE5qm5CmGxO8p1dR9v7bbqipm5pYRz8F6pQdWVHetCgA@mail.gmail.com>
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 ?
Cheers,
Ben.
next prev parent reply other threads:[~2013-06-13 22:53 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 [this message]
2013-06-13 22:56 ` Stephen Warren
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=1371163963.5555.25.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=SWarren@nvidia.com \
--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