linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mporter@linaro.org (Matt Porter)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] DT review process and standardization and ARM64 upstreaming
Date: Tue, 1 Apr 2014 15:50:57 -0400	[thread overview]
Message-ID: <20140401195057.GA5047@beef> (raw)

As an ARM platform co-maintainer, I'm interested in attending the ARM
kernel mini-summit to follow and participate in general discussions.
However, I have a couple areas of high interest.

In particular, I'm interested in the latest on the DT review process
as well as the plans to move the DTS out of the kernel and potential for
formal standardization. As pretty much everybody has ARM64 in the future,
I'm also interested in where efforts are already planned to share code
between ARM/ARM64 as well as understanding any differences in
upstreaming support for ARM64 platforms.

-Matt

                 reply	other threads:[~2014-04-01 19:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140401195057.GA5047@beef \
    --to=mporter@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).