From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] gpio: acpi: Add managed variant of acpi_dev_add_driver_gpios()
Date: Tue, 14 Mar 2017 14:27:06 +0200 [thread overview]
Message-ID: <1489494426.20145.237.camel@linux.intel.com> (raw)
In-Reply-To: <CACRpkdYZVY0jYLkuH3Ti7SUnV1Dz_SkkLKv0cyZdvVjiGOR9dQ@mail.gmail.com>
On Tue, 2017-03-14 at 10:58 +0100, Linus Walleij wrote:
> On Thu, Mar 2, 2017 at 2:48 PM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>
> > Introduce device managed variant of acpi_dev_add_driver_gpios() and
> > its
> > counterpart acpi_dev_remove_driver_gpios().
> >
> > The functions in most cases are used in driver's ->probe() and
> > ->remove() callbacks, that's why it's useful to have managed variant
> > of
> > them.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> >
> > This is supposed to go through GPIO tree.
> >
> > Linus, can you create an immutable branch that other subsystems can
> > use
> > it if needed?
>
> I have created ib-acpi-devm in the GPIO tree based on v4.11-rc1,
> applied
> this patch and merged that into my devel branch.
>
> Anyone who needs it can grab that branch, I will push it out later.
Thanks!
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2017-03-14 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 13:48 [PATCH v1] gpio: acpi: Add managed variant of acpi_dev_add_driver_gpios() Andy Shevchenko
2017-03-02 22:07 ` Rafael J. Wysocki
2017-03-14 9:58 ` Linus Walleij
2017-03-14 12:27 ` Andy Shevchenko [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=1489494426.20145.237.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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