From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ep93xx: pass platform startup data as __initdata
Date: Thu, 18 Mar 2010 10:43:40 +1300 [thread overview]
Message-ID: <4BA14D0C.40503@bluewatersys.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B0270842697636858D5BC@AUSP01VMBX24.collaborationhost.net>
H Hartley Sweeten wrote:
> A number of the peripherals for the ep93xx are registered at
> startup using platform_data that is passed from the board init
> code to the core code. This data is then copied to a local
> static variable in the core code. Since the data is copied,
> the original data can be marked as __initdata and discarded
> after startup is complete.
>
> This adds the __initdata tag to all the appropriate data in
> the various ep93xx board init's. Specifically, all the
> struct ep93xx_eth_data, struct ep93xxfb_mach_info, and
> struct i2c_gpio_platform_data.
>
> Also, document the various registration functions and note
> what data should be marked as __initdata.
>
> While here, also cleanup a couple over zealous whitespace tabs.
>
> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> Cc: Ryan Mallon <ryan@bluewatersys.com>
Looks good, and appears to work okay.
Acked-by: Ryan Mallon <ryan@bluewatersys.com>
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan at bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
prev parent reply other threads:[~2010-03-17 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 18:43 [PATCH] ep93xx: pass platform startup data as __initdata H Hartley Sweeten
2010-03-17 21:43 ` Ryan Mallon [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=4BA14D0C.40503@bluewatersys.com \
--to=ryan@bluewatersys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.