From: Andreas Schwab <schwab@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jean Delvare <khali@linux-fr.org>,
Tjernlund <tjernlund@tjernlund.se>,
linuxppc-dev@ozlabs.org, i2c@lm-sensors.org
Subject: Re: [RFC] Modifying i2c-core to support alias driver names compatible with device trees
Date: Thu, 08 Nov 2007 11:03:04 +0100 [thread overview]
Message-ID: <jey7d9t5pj.fsf@sykes.suse.de> (raw)
In-Reply-To: <20071108120535.769e4d73.sfr@canb.auug.org.au> (Stephen Rothwell's message of "Thu\, 8 Nov 2007 12\:05\:35 +1100")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> On Tue, 6 Nov 2007 15:39:42 -0500 "Jon Smirl" <jonsmirl@gmail.com> wrote:
>>
>> It was requested to split this code out into a separate thread....
>>
>> This code modifies the i2c-core to support lists of alias names in the
>> chip drivers.
>> For example: .aliases = (char const
>> *[]){"ricoh,rs5c372a","ricoh,rs5c372b","ricoh,rv5c386","ricoh,rv5c387a",
>> 0},
>
> You should not need the (char const *[]) casts at all.
It's not a cast, it's a compound literal. What it does is to create an
anonymous object, the address of which is the initializer for the
aliases pointer. Note that the anonymous object is not const qualified.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-11-08 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 20:39 [RFC] Modifying i2c-core to support alias driver names compatible with device trees Jon Smirl
2007-11-07 18:02 ` Jon Smirl
2007-11-08 1:05 ` Stephen Rothwell
2007-11-08 2:18 ` Jon Smirl
2007-11-08 10:03 ` Andreas Schwab [this message]
2007-11-08 5:27 ` Jon Smirl
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=jey7d9t5pj.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=tjernlund@tjernlund.se \
/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).