From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: mx28evk: remove flexcan_pdata __initconst attribute
Date: Fri, 11 Nov 2011 15:33:24 +0000 [thread overview]
Message-ID: <20111111153324.GF12913@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <65EE16ACC360FA4D99C96DC085B3F7722CED16@039-SN1MPN1-002.039d.mgd.msft.net>
On Fri, Nov 11, 2011 at 03:30:04PM +0000, Dong Aisheng-B29396 wrote:
> > -----Original Message-----
> > From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk]
> > Sent: Friday, November 11, 2011 11:28 PM
> > To: Dong Aisheng-B29396
> > Cc: Uwe Kleine-K?nig; Guo Shawn-R65073; s.hauer at pengutronix.de;
> > kernel at pengutronix.de; linux-arm-kernel at lists.infradead.org;
> > w.sang at pengutronix.de
> > Subject: Re: [PATCH 1/2] ARM: mx28evk: remove flexcan_pdata __initconst
> > attribute
> >
> > On Fri, Nov 11, 2011 at 03:25:01PM +0000, Dong Aisheng-B29396 wrote:
> > > -static struct fec_platform_data tx28_fec0_data = {
> > > +static struct fec_platform_data __initconst tx28_fec0_data = {
> >
> > No. It's spelt:
> >
> > static const struct fec_platform_data tx28_fec0_data __initconst = {
> Thanks for reminder, I missed the first const. :-)
That's not the only thing. Note the placement of the __initconst too.
next prev parent reply other threads:[~2011-11-11 15:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 15:12 [PATCH 1/2] ARM: mx28evk: remove flexcan_pdata __initconst attribute Dong Aisheng
2011-11-11 15:06 ` Uwe Kleine-König
2011-11-11 15:25 ` Dong Aisheng-B29396
2011-11-11 15:27 ` Russell King - ARM Linux
2011-11-11 15:30 ` Dong Aisheng-B29396
2011-11-11 15:33 ` Russell King - ARM Linux [this message]
2011-11-11 15:36 ` Dong Aisheng-B29396
2011-11-11 15:42 ` Uwe Kleine-König
2011-11-11 15:12 ` [PATCH 2/2] ARM: mxs: remove mmc_platform_data __initdata attribute Dong Aisheng
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=20111111153324.GF12913@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).