All of lore.kernel.org
 help / color / mirror / Atom feed
From: b.brezillon.dev@gmail.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] Following discussions
Date: Tue, 25 Mar 2014 07:03:58 +0100	[thread overview]
Message-ID: <53311C4E.9020708@gmail.com> (raw)

Hello,

As a contributor to atmel's at91 platform (and recently allwinner's sunxi)
I'm interested in following the ARM summit.
Moreover, I'll be involved in even more ARM related developments as part
of my future job at Free Electrons.

I'm particularly interested in DT bindings discussions to both follow DT
bindings progress/status on several subsystems and learn about their
limitations.

But more generally I'm interested in knowing where Linux dev for ARM 
platforms
is heading towards:
- are there any new subsystems in the pipeline ?
- are there any planned refactor in existing subsystems (or arch code) ?
- ...

Best Regards,

Boris

             reply	other threads:[~2014-03-25  6:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25  6:03 Boris BREZILLON [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-24 16:06 [ARM ATTEND] Following discussions Alexandre Belloni
2014-03-24 18:03 ` Rob Herring
2014-03-24 21:30   ` Alexandre Belloni

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=53311C4E.9020708@gmail.com \
    --to=b.brezillon.dev@gmail.com \
    --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.