From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] gpio: expose gpio_to_chip()
Date: Mon, 13 Jun 2011 10:43:29 +0200 [thread overview]
Message-ID: <BANLkTinMPXQcS2tZAJE57d=J4XbpGp_aFg@mail.gmail.com> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F001F3820B879F@AUSP01VMBX24.collaborationhost.net>
On Fri, Jun 10, 2011 at 5:57 PM, H Hartley Sweeten
<hartleys@visionengravers.com> wrote:
> On Friday, June 10, 2011 1:49 AM, Linus Walleij wrote:
>> This makes the gpio_to_chip() function available to drivers. The
>> usecase is when you want to add a few chip-specific operations
>> apart from the ones exposed in struct gpio_chip.
> (...)
>
> Linus,
>
> You'll need to fix a couple drivers for this to work. ?The symbol gpio_to_chip
> is a static symbol in a couple places other than gpiolib.c.
OK I fix! They are confusing anyway so should be patched pronto.
Linus Walleij
prev parent reply other threads:[~2011-06-13 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 8:49 [PATCH 1/2] gpio: expose gpio_to_chip() Linus Walleij
2011-06-10 15:57 ` H Hartley Sweeten
2011-06-13 8:43 ` Linus Walleij [this message]
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='BANLkTinMPXQcS2tZAJE57d=J4XbpGp_aFg@mail.gmail.com' \
--to=linus.walleij@linaro.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 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).