From: rubini@unipv.it (Alessandro Rubini)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm nomadik: Introduce plat-nomadik, MTU code re-organization
Date: Thu, 19 Nov 2009 11:08:38 +0100 [thread overview]
Message-ID: <20091119100838.GA13662@mail.gnudd.com> (raw)
In-Reply-To: <20091119094920.GG13376@n2100.arm.linux.org.uk>
> What's the reasoning for creating plat-nomadik? It's not clear from
> the comment above.
Other upcoming ST/ST-E SoCs share logic cells with the Nomadik SoC.
For example the arch-ux500 (for the 8500 and other SoCs) posted to
this list uses the same timer unit. I also have an RNG driver ready
to be submitted that is shared by the original Nomadik chip and these
other projects, but there will be other submitted drivers over time.
/alessandro
prev parent reply other threads:[~2009-11-19 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 21:39 [PATCH] arm nomadik: Introduce plat-nomadik, MTU code re-organization srinidhi kasagar
2009-11-19 9:49 ` Russell King - ARM Linux
2009-11-19 10:08 ` Alessandro Rubini [this message]
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=20091119100838.GA13662@mail.gnudd.com \
--to=rubini@unipv.it \
--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).