From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] DeviceTree status
Date: Tue, 25 Mar 2014 10:35:12 +0000 [thread overview]
Message-ID: <53315BE0.8030501@codethink.co.uk> (raw)
In-Reply-To: <CAL_JsqLe0s6iw_BuZg4B8RwByKSbVABLfTP9hiYhTfzvaaQp_A@mail.gmail.com>
On 24/03/14 14:55, Rob Herring wrote:
> I will be attending ELC. I think I may be the only DT maintainer
> attending (the rest were too scared).
I thought Grant was listed?
> For the ARM summit, I can give a summary of what's happened in DT land
> since the last ARM summit. There's been some good progress although
> probably not as much as anyone would like. Given the last summit, I'm
> sure there is more to discuss. If not, I'm available for beers to
> celebrate solving all the issues. ;)
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-03-25 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 14:55 [ARM ATTEND] DeviceTree status Rob Herring
2014-03-25 10:35 ` Ben Dooks [this message]
2014-03-28 23:52 ` Grant Likely
2014-03-31 18:01 ` Florian Fainelli
2014-04-02 15:35 ` Kevin Hilman
2014-04-03 5:16 ` Olof Johansson
2014-04-03 11:31 ` Laurent Pinchart
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=53315BE0.8030501@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.