From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 1/1] kirkwood: Add iconnect support
Date: Wed, 18 Apr 2012 14:53:40 +0200 [thread overview]
Message-ID: <871unlyze3.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <20120418104002.GA15924@lunn.ch> (Andrew Lunn's message of "Wed, 18 Apr 2012 12:40:02 +0200")
Andrew Lunn <andrew@lunn.ch> writes:
Hi,
>> > +
>> > +#define ICONNECT_BLINK_HALF_PERIOD 100
>> > +
>> > +static int iconnect_blink_set(unsigned gpio, int state,
>>
>>__init ?
>
> Hi Jason
>
> It is correct without __init. This function will get called when you
> play with /sys/class/leds/*/trigger.
>
> However, this is the second public instance of this function, it is
> also in mach-orion5x/dns323-setup.c.
yeah, I know. I initially planned to send a patchset adding iconnect
support and putting this function into something like gpio.c but I
forgot about it when converting my first iconnect patch into DT. Any
objection about sending a patch doing that once I manage to merge the
iconnect support (and of course, in this case, feel free to remind me
of it if I forget to do it ) ?
Arnaud
next parent reply other threads:[~2012-04-18 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120418104002.GA15924@lunn.ch>
2012-04-18 12:53 ` Arnaud Patard (Rtp) [this message]
2012-04-18 14:33 ` [patch 1/1] kirkwood: Add iconnect support Jason Cooper
2012-04-16 22:05 [patch 0/1] Kirwood: Add Iomega Iconnect support Arnaud Patard (Rtp)
2012-04-16 22:05 ` [patch 1/1] kirkwood: Add iconnect support Arnaud Patard (Rtp)
2012-04-17 14:27 ` Jason Cooper
2012-04-17 18:53 ` Arnaud Patard (Rtp)
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=871unlyze3.fsf@lebrac.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--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.