From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] gpiolib-acpi: introduce acpi_get_gpio_by_index() helper
Date: Fri, 12 Apr 2013 09:57:11 +0300 [thread overview]
Message-ID: <20130412065710.GM1283@intel.com> (raw)
In-Reply-To: <CACRpkdYiNOLVAgZVhZG3OaJw5ZZ4OM8RPafCxPPfMWo2gVM=dg@mail.gmail.com>
On Fri, Apr 12, 2013 at 12:35:05AM +0200, Linus Walleij wrote:
> On Thu, Apr 11, 2013 at 9:29 AM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
>
> > Grant and Linus W,
> >
> > Do you have any comments on this patch? Could it still be merged for 3.10?
>
> No and yes.
>
> Applied and pushed for linux-next now.
Thanks!
> Sorry for taking so long, I was confused by the discussion.
np. We probably need to add another ACPI GPIO helper function to get all
the GPIOs but I guess we can do that once a need emerges. For a single GPIO
(like the patch here does) we know already from internal discussion that it
will be needed.
> I had to use some fuzzing to apply the patch, please check the
> result in linux-next.
Looks good to me.
next prev parent reply other threads:[~2013-04-12 6:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 10:56 [PATCH] gpiolib-acpi: introduce acpi_get_gpio_by_index() helper Mika Westerberg
2013-04-03 11:04 ` Rafael J. Wysocki
2013-04-11 7:29 ` Mika Westerberg
2013-04-11 22:35 ` Linus Walleij
2013-04-12 6:57 ` Mika Westerberg [this message]
2013-04-04 9:19 ` Benjamin Tissoires
2013-04-04 9:38 ` Mika Westerberg
2013-04-04 9:42 ` Benjamin Tissoires
2013-04-04 9:57 ` Mika Westerberg
2013-04-04 10:01 ` Benjamin Tissoires
2013-04-04 10:13 ` Mika Westerberg
2013-04-11 22:33 ` Linus Walleij
2013-04-11 22:43 ` Rafael J. Wysocki
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=20130412065710.GM1283@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=rafael.j.wysocki@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.