From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM+ARM64: constify of_device_ids
Date: Wed, 10 Sep 2014 10:26:16 +0200 [thread overview]
Message-ID: <1410337579-23466-1-git-send-email-u.kleine-koenig@pengutronix.de> (raw)
Hello,
most of_device_ids can (and should) be const as the driver core cannot
handle changes to compatible strings. So I checked all non-const
of_device_ids and they can all be marked as const, for omap2 after some
function parameters get a const annotation, too.
I split of the changes to mach-omap2 because there (as noted above) some
functions need a change there, too.
Should I split further by platform? Who is willing to take these
patches?
Best regards
Uwe
Uwe Kleine-K?nig (3):
ARM: OMAP2+: make of_device_ids const
ARM: make of_device_ids const
ARM64: make of_device_ids const
arch/arm/kernel/perf_event_cpu.c | 2 +-
arch/arm/mach-at91/at91rm9200_time.c | 2 +-
arch/arm/mach-at91/at91sam9263_devices.c | 2 +-
arch/arm/mach-at91/at91sam926x_time.c | 2 +-
arch/arm/mach-at91/clock.c | 4 ++--
arch/arm/mach-at91/setup.c | 6 +++---
arch/arm/mach-davinci/da8xx-dt.c | 2 +-
arch/arm/mach-imx/mmdc.c | 2 +-
arch/arm/mach-keystone/pm_domain.c | 2 +-
arch/arm/mach-mmp/time.c | 2 +-
arch/arm/mach-mvebu/coherency.c | 2 +-
arch/arm/mach-mvebu/pmsu.c | 2 +-
arch/arm/mach-omap2/board-generic.c | 2 +-
arch/arm/mach-omap2/common.h | 2 +-
arch/arm/mach-omap2/gpmc.c | 2 +-
arch/arm/mach-omap2/irq.c | 2 +-
arch/arm/mach-omap2/pdata-quirks.c | 2 +-
arch/arm/mach-omap2/prm_common.c | 2 +-
arch/arm/mach-omap2/timer.c | 6 +++---
arch/arm/mach-prima2/platsmp.c | 2 +-
arch/arm/mach-sunxi/sunxi.c | 2 +-
arch/arm64/kernel/perf_event.c | 2 +-
22 files changed, 27 insertions(+), 27 deletions(-)
--
2.1.0
next reply other threads:[~2014-09-10 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 8:26 Uwe Kleine-König [this message]
2014-09-10 8:26 ` [PATCH 1/3] ARM: OMAP2+: make of_device_ids const Uwe Kleine-König
2014-09-11 17:39 ` Tony Lindgren
2014-09-11 19:01 ` Uwe Kleine-König
2014-09-11 19:14 ` Tony Lindgren
2014-09-11 19:42 ` Uwe Kleine-König
2014-09-11 19:47 ` Tony Lindgren
2014-09-11 19:52 ` Uwe Kleine-König
2014-09-11 20:10 ` Tony Lindgren
2014-09-11 19:14 ` Uwe Kleine-König
2014-09-10 8:26 ` [PATCH 2/3] ARM: " Uwe Kleine-König
2014-09-10 15:17 ` Jason Cooper
2014-09-10 8:26 ` [PATCH 3/3] ARM64: " Uwe Kleine-König
2014-09-15 13:11 ` Catalin Marinas
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=1410337579-23466-1-git-send-email-u.kleine-koenig@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).