From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: (arm-)global platform device registration functions
Date: Wed, 29 Dec 2010 17:25:12 +0100 [thread overview]
Message-ID: <20101229162512.GI14221@pengutronix.de> (raw)
Hello,
some time ago I started to dynamically allocate platform_devices for
arm/plat-mxc. For that purpose I added many functions, see
arch/arm/plat-mxc/include/mach/devices-common.h [1]. Now arm/arch-mxs
want to do the same, so I wonder if it would be sensible to do something
like this more globally (either for arm or better kernel global).
Thoughts?
Best regards
Uwe
[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=arch/arm/plat-mxc/include/mach/devices-common.h;hb=HEAD
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next reply other threads:[~2010-12-29 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 16:25 Uwe Kleine-König [this message]
2010-12-29 20:37 ` (arm-)global platform device registration functions Andrew Morton
2010-12-29 21:18 ` Uwe Kleine-König
2010-12-30 10:03 ` Arnd Bergmann
2010-12-30 10:15 ` Uwe Kleine-König
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=20101229162512.GI14221@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).