From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robherring2@gmail.com>
Cc: "Rowand, Frank" <Frank.Rowand@sonymobile.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"devicetree-compiler@vger.kernel.org"
<devicetree-compiler@vger.kernel.org>,
"linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>,
"celinux-dev@lists.celinuxforum.org"
<celinux-dev@lists.celinuxforum.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Matt Porter <mporter@konsulko.com>, Jon Loeliger <jdl@jdl.com>,
Gaurav Minocha <gaurav.minocha.os@gmail.com>
Subject: Re: Invitation and RFC: Linux Plumbers Device Tree track proposed
Date: Tue, 14 Apr 2015 22:58:46 +0200 [thread overview]
Message-ID: <10482596.MaespZJCtk@wuerfel> (raw)
In-Reply-To: <CAL_JsqL0FdvKtGTxFNYxtrGWkm3z-1m0v9dHwYezCtkFOW6EgQ@mail.gmail.com>
On Tuesday 14 April 2015 10:36:15 Rob Herring wrote:
>
> > 4) Identifying additional people who should attend the device tree track.
>
> Arnd Bergmann
> Matt Porter
> Jon Loeliger
> Gaurav Minocha
Sorry, I won't be there. I should have replied earlier, but I'll be on
parental leave at the time.
Arnd
next prev parent reply other threads:[~2015-04-14 20:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 19:20 Invitation and RFC: Linux Plumbers Device Tree track proposed Rowand, Frank
[not found] ` <8251B150E4DF5041A62C3EA9F0AB2E0603A53FE1082E-6yWnlZQfN9JoBVljSLT0Ysm4BeyDBExM@public.gmane.org>
2015-04-12 0:05 ` Rob Landley
2015-04-12 0:05 ` [Celinux-dev] " Rob Landley
[not found] ` <CAOS_Y6Qmt2KTRu6urPs-Y1e2Xv1QPNTaQHH4_N8Kk8XU7n+ecQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-12 7:53 ` Geert Uytterhoeven
2015-04-12 7:53 ` Geert Uytterhoeven
2015-04-13 5:13 ` David Gibson
2015-04-13 5:13 ` David Gibson
2015-04-14 15:36 ` Rob Herring
2015-04-14 15:36 ` Rob Herring
[not found] ` <CAL_JsqL0FdvKtGTxFNYxtrGWkm3z-1m0v9dHwYezCtkFOW6EgQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-14 17:14 ` Mark Rutland
2015-04-14 17:14 ` Mark Rutland
2015-04-14 20:58 ` Arnd Bergmann [this message]
2015-05-26 16:31 ` Jon Loeliger
2015-05-26 16:31 ` Jon Loeliger
2015-05-01 13:32 ` Matt Porter
2015-05-01 21:22 ` [Celinux-dev] " Rob Landley
2015-05-01 21:22 ` Rob Landley
[not found] ` <5543EE80.5060109-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
2015-05-02 7:51 ` Geert Uytterhoeven
2015-05-02 7:51 ` [Celinux-dev] " Geert Uytterhoeven
2015-05-04 23:20 ` Rob Herring
2015-05-04 23:20 ` Rob Herring
[not found] ` <CAL_JsqKkZYEMdYmh=JkA6O34a+7mKy=SgB2XxzgTM70mihgQeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-05 7:34 ` Geert Uytterhoeven
2015-05-05 7:34 ` Geert Uytterhoeven
[not found] ` <CAMuHMdV7xfbBYL5fhudObdwNVJ0L_1_h0ozT+U4Lpx=Mu9UGhw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-05 19:32 ` Rob Herring
2015-05-05 19:32 ` [Celinux-dev] " Rob Herring
2015-05-06 3:28 ` David Gibson
2015-05-06 3:28 ` David Gibson
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=10482596.MaespZJCtk@wuerfel \
--to=arnd@arndb.de \
--cc=Frank.Rowand@sonymobile.com \
--cc=celinux-dev@lists.celinuxforum.org \
--cc=devicetree-compiler@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gaurav.minocha.os@gmail.com \
--cc=jdl@jdl.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@konsulko.com \
--cc=robherring2@gmail.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 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.