From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] Marvell development, ARM discussions
Date: Fri, 2 Aug 2013 11:39:11 +0200 [thread overview]
Message-ID: <20130802113911.44b74d9e@skate> (raw)
Hello,
I'm working quite actively on Marvell ARM SoC support in the kernel
(Armada 370, Armada XP, Kirkwood, etc.). I don't have any specific
topic to put on the table as others have already mentioned them, but
I'm interested in following where the ARM code is heading to. I'm
especially interested about the Device Tree discussions, arch/arm SoC
organization, kernel data bloat.
I did had the chance to attend the ARM kernel mini-summit last year and
I found it very useful. I'll be in Edinburgh this year, so attending
the ARM kernel mini-summit would be very interesting.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
reply other threads:[~2013-08-02 9:39 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=20130802113911.44b74d9e@skate \
--to=thomas.petazzoni@free-electrons.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 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).