From: Alex Courbot <acourbot@nvidia.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
David Cohen <david.a.cohen@intel.com>,
Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v5 0/2] gpiolib, sfi: introduce SFI GPIO helpers
Date: Tue, 10 Dec 2013 12:05:02 +0900 [thread overview]
Message-ID: <52A684DE.9060605@nvidia.com> (raw)
In-Reply-To: <1386600421-16463-1-git-send-email-andriy.shevchenko@linux.intel.com>
On 12/09/2013 11:46 PM, Andy Shevchenko wrote:
> Here is a fifth [1] version of the SFI GPIO helpers. This series contains SFI
> GPIO helpers along with the update of GPIO library to lookup for SFI resources.
>
> It has been tested on Medfield device on top of recent linux-gpio/for-next +
> Mika's ACPI gpio patches [2].
>
> Changes since v4:
> - fix one compilation warning
>
> [1] https://lkml.org/lkml/2013/6/5/316
> [2] http://www.spinics.net/lists/linux-acpi/msg47572.html
I commented on the v1 of this series about a potential lookup issue -
while I totally agree with the overall idea, I'd like to see this issue
solved before I give my ack.
prev parent reply other threads:[~2013-12-10 3:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 14:46 [PATCH v5 0/2] gpiolib, sfi: introduce SFI GPIO helpers Andy Shevchenko
2013-12-09 14:47 ` [PATCH v5 1/2] SFI: store GPIO table and export lookup function Andy Shevchenko
2013-12-10 3:08 ` Alex Courbot
2013-12-09 14:47 ` [PATCH v5 2/2] gpiolib: append SFI helpers for GPIO API Andy Shevchenko
2013-12-09 15:01 ` [PATCH v5 0/2] gpiolib, sfi: introduce SFI GPIO helpers Mika Westerberg
2013-12-10 3:05 ` Alex Courbot [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=52A684DE.9060605@nvidia.com \
--to=acourbot@nvidia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david.a.cohen@intel.com \
--cc=lenb@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=sathyanarayanan.kuppuswamy@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 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.