From: Ian Lartey <ian@slimlogic.co.uk>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
Graeme Gregory <gg@slimlogic.co.uk>
Subject: Re: [PATCH] gpio: palmas: add in GPIO support for palmas charger
Date: Fri, 22 Mar 2013 08:37:57 +0000 [thread overview]
Message-ID: <514C1865.1020602@slimlogic.co.uk> (raw)
In-Reply-To: <CACRpkdZyBB+Bqevgi7dGw+nWu245RgKNv7Cpim4YRuhYbcP1xw@mail.gmail.com>
On 22/03/13 07:55, Linus Walleij wrote:
> On Tue, Feb 26, 2013 at 3:14 PM, Laxman Dewangan <ldewangan@nvidia.com> wrote:
>
>> On Tuesday 26 February 2013 07:43 PM, Ian Lartey wrote:
>> On 26/02/13 13:58, Laxman Dewangan wrote:
>>
>> On Tuesday 26 February 2013 06:51 PM, Ian Lartey wrote:
>>
>> this patch depenfs on [PATCH] mfd: palmas: is_palmas_charger needed by
>> multiple drivers
>>
>> Palmas charger has 16 GPIOs
>> add palmas_gpio_[read|write|update] api to take account
>> second bank of GPIOs
>>
>> Signed-off-by: Ian Lartey <ian@slimlogic.co.uk>
>> Signed-off-by: Graeme Gregory <gg@slimlogic.co.uk>
>
> Is something happening in this series?
>
> I'm ignoring it for now since the last activity in the thread was
> some concerns from Laxman.
>
> Yours,
> Linus Walleij
>
Yes there's going to be an patch series update [v9] posted today.
Ian
next prev parent reply other threads:[~2013-03-22 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 13:21 [PATCH] gpio: palmas: add in GPIO support for palmas charger Ian Lartey
2013-02-26 13:58 ` Laxman Dewangan
2013-02-26 14:13 ` Ian Lartey
[not found] ` <512CC357.9040600@nvidia.com>
2013-03-22 7:55 ` Linus Walleij
2013-03-22 8:37 ` Ian Lartey [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-26 14:49 Ian Lartey
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=514C1865.1020602@slimlogic.co.uk \
--to=ian@slimlogic.co.uk \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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