From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>, Keerthy <j-keerthy@ti.com>,
Tero Kristo <t-kristo@ti.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Ladislav Michl <ladis@linux-mips.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] gpio: omap: Remove custom PM calls and use cpu_pm instead
Date: Fri, 14 Sep 2018 06:20:28 -0700 [thread overview]
Message-ID: <20180914132028.GM5662@atomide.com> (raw)
In-Reply-To: <CACRpkdbjkL=Aq1ktMFT1jwOrOwby5xZgh-GC0JAheR9UU71Ajg@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [180914 09:13]:
> On Tue, Sep 11, 2018 at 8:37 PM Tony Lindgren <tony@atomide.com> wrote:
>
> > Linus, once people are happy with these, can you maybe set up an
> > immutable branch with both patches in it?
>
> Sure thing, just awaiting the final ACKed version.
Looks like I need a bit more time though to sort out the suspend/resume
though. And it seems we can now finally drop the pm_runtime_irq_safe too :)
> There are some more OMAP patches floating I see, so maybe
> a branch with all of them on for testing purposes and coordination?
OK sounds good to me thanks.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] gpio: omap: Remove custom PM calls and use cpu_pm instead
Date: Fri, 14 Sep 2018 06:20:28 -0700 [thread overview]
Message-ID: <20180914132028.GM5662@atomide.com> (raw)
In-Reply-To: <CACRpkdbjkL=Aq1ktMFT1jwOrOwby5xZgh-GC0JAheR9UU71Ajg@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [180914 09:13]:
> On Tue, Sep 11, 2018 at 8:37 PM Tony Lindgren <tony@atomide.com> wrote:
>
> > Linus, once people are happy with these, can you maybe set up an
> > immutable branch with both patches in it?
>
> Sure thing, just awaiting the final ACKed version.
Looks like I need a bit more time though to sort out the suspend/resume
though. And it seems we can now finally drop the pm_runtime_irq_safe too :)
> There are some more OMAP patches floating I see, so maybe
> a branch with all of them on for testing purposes and coordination?
OK sounds good to me thanks.
Tony
next prev parent reply other threads:[~2018-09-14 13:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 18:37 [PATCH] gpio: omap: Remove custom PM calls and use cpu_pm instead Tony Lindgren
2018-09-11 18:37 ` Tony Lindgren
2018-09-11 19:40 ` Ladislav Michl
2018-09-11 19:40 ` Ladislav Michl
2018-09-11 23:28 ` Tony Lindgren
2018-09-11 23:28 ` Tony Lindgren
2018-09-11 23:34 ` Tony Lindgren
2018-09-11 23:34 ` Tony Lindgren
2018-09-12 0:29 ` Grygorii Strashko
2018-09-12 0:29 ` Grygorii Strashko
2018-09-12 0:41 ` Tony Lindgren
2018-09-12 0:41 ` Tony Lindgren
2018-09-14 9:09 ` Linus Walleij
2018-09-14 9:09 ` Linus Walleij
2018-09-14 13:20 ` Tony Lindgren [this message]
2018-09-14 13:20 ` Tony Lindgren
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=20180914132028.GM5662@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=gnurou@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=j-keerthy@ti.com \
--cc=ladis@linux-mips.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=t-kristo@ti.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.