From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCHv2 0/3] omap gpio add level idle, cpu_pm and drop runtime_irq_safe
Date: Tue, 25 Sep 2018 07:35:49 -0700 [thread overview]
Message-ID: <20180925143549.GM5662@atomide.com> (raw)
In-Reply-To: <CACRpkdao5j14OXAvL==008gnquvKpzuPwkK+vA2jTeyy9H+gcA@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [180925 06:57]:
> On Thu, Sep 20, 2018 at 9:35 PM Tony Lindgren <tony@atomide.com> wrote:
>
> > Linus, assuming people are happy with these, I'd appreciate an immutable branch
> > with these in case we run into merge conflicts for arch/arm/mach-omap2 changes.
>
> I created an immutable branch named "ib-omap" yesterday:
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/log/?h=ib-omap
>
> It passed build tests this morning so I merged this into my "devel" branch
> for next.
OK thanks!
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/3] omap gpio add level idle, cpu_pm and drop runtime_irq_safe
Date: Tue, 25 Sep 2018 07:35:49 -0700 [thread overview]
Message-ID: <20180925143549.GM5662@atomide.com> (raw)
In-Reply-To: <CACRpkdao5j14OXAvL==008gnquvKpzuPwkK+vA2jTeyy9H+gcA@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [180925 06:57]:
> On Thu, Sep 20, 2018 at 9:35 PM Tony Lindgren <tony@atomide.com> wrote:
>
> > Linus, assuming people are happy with these, I'd appreciate an immutable branch
> > with these in case we run into merge conflicts for arch/arm/mach-omap2 changes.
>
> I created an immutable branch named "ib-omap" yesterday:
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/log/?h=ib-omap
>
> It passed build tests this morning so I merged this into my "devel" branch
> for next.
OK thanks!
Tony
next prev parent reply other threads:[~2018-09-25 14:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 19:35 [PATCHv2 0/3] omap gpio add level idle, cpu_pm and drop runtime_irq_safe Tony Lindgren
2018-09-20 19:35 ` Tony Lindgren
2018-09-20 19:35 ` [PATCH 1/3] gpio: omap: Add level wakeup handling for omap4 based SoCs Tony Lindgren
2018-09-20 19:35 ` Tony Lindgren
2018-09-21 5:45 ` Keerthy
2018-09-21 5:45 ` Keerthy
2018-09-20 19:35 ` [PATCH 2/3] gpio: omap: Remove custom PM calls and use cpu_pm instead Tony Lindgren
2018-09-20 19:35 ` Tony Lindgren
2018-09-20 23:01 ` Grygorii Strashko
2018-09-20 23:01 ` Grygorii Strashko
2018-09-20 23:47 ` Tony Lindgren
2018-09-20 23:47 ` Tony Lindgren
2018-09-21 0:58 ` Grygorii Strashko
2018-09-21 0:58 ` Grygorii Strashko
2018-09-20 19:35 ` [PATCH 3/3] gpio: omap: Get rid of pm_runtime_irq_safe() Tony Lindgren
2018-09-20 19:35 ` Tony Lindgren
2018-09-22 3:12 ` [PATCHv2 0/3] omap gpio add level idle, cpu_pm and drop runtime_irq_safe Grygorii Strashko
2018-09-22 3:12 ` Grygorii Strashko
2018-09-25 6:53 ` Linus Walleij
2018-09-25 6:53 ` Linus Walleij
2018-09-25 14:35 ` Tony Lindgren [this message]
2018-09-25 14:35 ` 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=20180925143549.GM5662@atomide.com \
--to=tony@atomide.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.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 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.