From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: slot-gpio: Add support for power gpios
Date: Sun, 09 Sep 2012 22:55:36 -0400 [thread overview]
Message-ID: <877gs2zivr.fsf@octavius.laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1209092325350.11567@axis700.grange> (Guennadi Liakhovetski's message of "Mon, 10 Sep 2012 00:05:11 +0200 (CEST)")
Hi Guennadi,
Thanks for getting to this review so quickly! I agree with all of your
comments. I'm sending out v2 of both patches now.
On Sun, Sep 09 2012, Guennadi Liakhovetski wrote:
>> The zero-length array trick might be becoming unmaintainable as we add
>> more labels to the struct like this. Do you think we should keep it
>> as-is, or change to individual allocations? Thanks!
>
> Yeah, it's becoming a bit messy... But I also don't find dynamically
> allocating multiple tiny memory areas with the same life-cycle
> particularly elegant... Are you expecting many more GPIOs to be added
> here?
No, I don't expect needing to add more -- I just found myself wondering
if there was a better way and thought I'd mention it. Performing
multiple allocations is unattractive too, I agree.
> What we could do, though, we could add macros for various pin function
> names, their lengths, offsets and the total length, to make the
> calculations look less cryptic. Would that be a good alternative?
Adding the comments is probably fine for now; I'd be okay with waiting
to see if we need more GPIO types and revisiting a better solution then.
Thanks!
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-09-10 2:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 3:01 [PATCH] mmc: slot-gpio: Add support for power gpios Chris Ball
2012-09-09 22:05 ` Guennadi Liakhovetski
2012-09-10 2:55 ` Chris Ball [this message]
2012-09-10 3:01 ` [PATCH v2] " Chris Ball
2012-09-10 21:48 ` Guennadi Liakhovetski
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=877gs2zivr.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-mmc@vger.kernel.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