From: David Cohen <david.a.cohen@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, sfi-devel@simplefirmware.org,
linux-gpio@vger.kernel.org,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] gpiolib: append SFI helpers for GPIO API
Date: Thu, 17 Oct 2013 10:06:38 -0700 [thread overview]
Message-ID: <5260191E.4060603@linux.intel.com> (raw)
In-Reply-To: <1382013695.29062.141.camel@smile>
On 10/17/2013 05:41 AM, Andy Shevchenko wrote:
> On Wed, 2013-10-16 at 20:03 -0700, David Cohen wrote:
>> From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>>
>> To support some (legacy) firmwares and platforms let's make life easier for
>> their customers.
>>
>
>
>> +int sfi_get_gpio_by_name(const char *name)
>> +{
>> + struct sfi_gpio_table_entry *pentry = sfi_gpio_table;
>> + int i;
>> +
>> + if (!pentry)
>> + return -1;
>
> ^^^^ It seems an old version.
>
> New version was published while ago and even has an ACK from Linus:
>
> http://www.spinics.net/lists/kernel/msg1545960.html
Interesting :)
I got this patch cooking in our internal tree for quite some time.
Didn't realize about the new version. I'm waiting it to be merged to
send an Intel Mid patch that depends on that.
Please, ignore this version and consider the one pointed out by Andy.
Br, David Cohen
>
>
next prev parent reply other threads:[~2013-10-17 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 3:03 [PATCH] gpiolib: append SFI helpers for GPIO API David Cohen
2013-10-17 12:41 ` Andy Shevchenko
2013-10-17 17:06 ` David Cohen [this message]
2013-11-12 18:55 ` Linus Walleij
2013-11-13 12:16 ` Andy Shevchenko
2013-11-13 17:41 ` David Cohen
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=5260191E.4060603@linux.intel.com \
--to=david.a.cohen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sfi-devel@simplefirmware.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).