From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Alexandre Courbot <acourbot@nvidia.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
David Cohen <david.a.cohen@intel.com>,
Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v4 2/2] gpiolib: append SFI helpers for GPIO API
Date: Mon, 09 Dec 2013 16:22:56 +0200 [thread overview]
Message-ID: <1386598976.1871.136.camel@smile> (raw)
In-Reply-To: <CACRpkdYKK9LAGEPVWY422o4D-JG-Gxq-djydXW+MJXLXmpaEwA@mail.gmail.com>
On Mon, 2013-12-09 at 15:15 +0100, Linus Walleij wrote:
> On Mon, Dec 9, 2013 at 2:32 PM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>
> > Linus, by the way, there is a minor issue in code (see above comment). I
> > could fix by myself if you want me to do.
>
> Just respin it while we're waiting for Len's ACK...
Will send v5 soon.
>
> Maybe he could use a co-maintainer for SFI?
Let's ask David. At least he is closer to that SFI stuff than me.
David, who is the best person to get an Ack for SFI stuff nowadays?
>
> Yours,
> Linus Walleij
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2013-12-09 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 11:50 [PATCH v4 0/2] gpiolib, sfi: introduce SFI GPIO helpers Andy Shevchenko
2013-12-09 11:50 ` [PATCH v4 1/2] SFI: store GPIO table and export lookup function Andy Shevchenko
2013-12-09 11:50 ` [PATCH v4 2/2] gpiolib: append SFI helpers for GPIO API Andy Shevchenko
2013-12-09 13:04 ` Mika Westerberg
2013-12-09 13:02 ` Andy Shevchenko
2013-12-09 13:27 ` Linus Walleij
2013-12-09 13:32 ` Andy Shevchenko
2013-12-09 14:15 ` Linus Walleij
2013-12-09 14:22 ` Andy Shevchenko [this message]
2013-12-10 2:46 ` Alex Courbot
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=1386598976.1871.136.camel@smile \
--to=andriy.shevchenko@linux.intel.com \
--cc=acourbot@nvidia.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 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).