From: Bill Gatliff <bgat@billgatliff.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: linux-embedded@vger.kernel.org
Subject: Re: [PWM v5 1/3] PWM: Implement a generic PWM framework
Date: Sun, 20 Feb 2011 22:42:10 -0600 [thread overview]
Message-ID: <AANLkTinqCoHX6rpcY51Prc1h09VBHpqtVEo4-jHY1Acm@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=egAxrcGxRsAqYwnv0=DgxQuL_Gqd5-AR7=3Zg@mail.gmail.com>
Mike:
On Sun, Feb 20, 2011 at 9:33 PM, Mike Frysinger <vapier.adi@gmail.com> wrote:
> On Sun, Feb 20, 2011 at 22:18, Bill Gatliff wrote:
>> On Sun, Feb 20, 2011 at 4:46 PM, Mike Frysinger <vapier.adi@gmail.com> wrote:
>>>> +static const struct attribute_group pwm_device_attr_group = {
>>>> + .attrs = (struct attribute **) pwm_attrs,
>>>> +};
>>>
>>> should attribute_group have its attrs member constified ?
>>
>> Isn't it already, given that the pwm_device_attr_group definition is const?
>
> if it were already, you wouldnt need that cast
Aah, so you are suggesting that I patch the attribute_group structure
definition, no?
Scary. Not. My. Code. :)
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2011-02-21 4:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 4:10 [PWM v5 0/3] Implement a generic PWM framework Bill Gatliff
2011-02-20 4:10 ` [PWM v5 1/3] PWM: " Bill Gatliff
2011-02-20 22:46 ` Mike Frysinger
2011-02-21 0:38 ` Bill Gatliff
2011-02-21 0:58 ` Mike Frysinger
2011-02-21 3:18 ` Bill Gatliff
2011-02-21 3:33 ` Mike Frysinger
2011-02-21 4:42 ` Bill Gatliff [this message]
2011-02-20 4:10 ` [PWM v5 2/3] PWM: GPIO+hrtimer device emulation Bill Gatliff
2011-02-20 22:35 ` Mike Frysinger
2011-02-21 0:39 ` Bill Gatliff
2011-02-20 4:10 ` [PWM v5 3/3] PWM: Atmel PWMC driver Bill Gatliff
2011-02-20 22:31 ` Mike Frysinger
2011-02-21 0:40 ` Bill Gatliff
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=AANLkTinqCoHX6rpcY51Prc1h09VBHpqtVEo4-jHY1Acm@mail.gmail.com \
--to=bgat@billgatliff.com \
--cc=linux-embedded@vger.kernel.org \
--cc=vapier.adi@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).