From: Janusz Krzysztofik <jmkrzyszt@gmail.com> To: Tony Lindgren <tony@atomide.com> Cc: Linus Walleij <linus.walleij@linaro.org>, Aaro Koskinen <aaro.koskinen@iki.fi>, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/3] ARM: OMAP1: ams-delta: Clean up GPIO setup for MODEM Date: Fri, 21 Sep 2018 00:43:49 +0200 [thread overview] Message-ID: <4137539.DlEMru2qd5@z50> (raw) In-Reply-To: <20180920212326.GS5662@atomide.com> Hi Tony, On Thursday, September 20, 2018 11:23:26 PM CEST Tony Lindgren wrote: > * Janusz Krzysztofik <jmkrzyszt@gmail.com> [180910 21:52]: > > On Monday, September 10, 2018 1:44:16 AM CEST Janusz Krzysztofik wrote: > > > > > > Convert modem related GPIO setup from integer space to GPIO descriptors. > > > Also, restore original initialization order of the MODEM device and its > > > related GPIO pins. > > > > > > Cleanup of MODEM relaated regulator setup is postponed while waiting for > > > upcoming conversion of fixed regulator API to GPIO descriptors. > > > > > > > > > Janusz Krzysztofik (3): > > > ARM: OMAP1: ams-delta: assign MODEM IRQ from GPIO descriptor > > > ARM: OMAP1: ams-delta: initialize latch2 pins to safe values > > > ARM: OMAP1: ams-delta: register MODEM device earlier > > > > > > > > > Changelog: > > > v2: > > > - rebased on v4.19-rc1 > > > > Hi Tony, > > > > I forgot to mention: please apply on top of "[PATCH v3 0/3] ARM: OMAP1: ams- > > delta: Complete driver gpiod migration" series. Sorry. > > Hmm but then in that thread you said that it won't apply.. So I'm applying > this series into omap-for-v4.20/omap1 branch. I just modified the second > patch in this series for the unchanged header location. OK, thank you. Janusz > I suggest you send the mtd patch separately to mtd maintainers, the fb patch > separately to fb maintainers and then let's do the header move after all > those are merged as a clean-up. That avoids some dependencies between these > branches. > > Regards, > > Tony >
WARNING: multiple messages have this Message-ID (diff)
From: jmkrzyszt@gmail.com (Janusz Krzysztofik) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 0/3] ARM: OMAP1: ams-delta: Clean up GPIO setup for MODEM Date: Fri, 21 Sep 2018 00:43:49 +0200 [thread overview] Message-ID: <4137539.DlEMru2qd5@z50> (raw) In-Reply-To: <20180920212326.GS5662@atomide.com> Hi Tony, On Thursday, September 20, 2018 11:23:26 PM CEST Tony Lindgren wrote: > * Janusz Krzysztofik <jmkrzyszt@gmail.com> [180910 21:52]: > > On Monday, September 10, 2018 1:44:16 AM CEST Janusz Krzysztofik wrote: > > > > > > Convert modem related GPIO setup from integer space to GPIO descriptors. > > > Also, restore original initialization order of the MODEM device and its > > > related GPIO pins. > > > > > > Cleanup of MODEM relaated regulator setup is postponed while waiting for > > > upcoming conversion of fixed regulator API to GPIO descriptors. > > > > > > > > > Janusz Krzysztofik (3): > > > ARM: OMAP1: ams-delta: assign MODEM IRQ from GPIO descriptor > > > ARM: OMAP1: ams-delta: initialize latch2 pins to safe values > > > ARM: OMAP1: ams-delta: register MODEM device earlier > > > > > > > > > Changelog: > > > v2: > > > - rebased on v4.19-rc1 > > > > Hi Tony, > > > > I forgot to mention: please apply on top of "[PATCH v3 0/3] ARM: OMAP1: ams- > > delta: Complete driver gpiod migration" series. Sorry. > > Hmm but then in that thread you said that it won't apply.. So I'm applying > this series into omap-for-v4.20/omap1 branch. I just modified the second > patch in this series for the unchanged header location. OK, thank you. Janusz > I suggest you send the mtd patch separately to mtd maintainers, the fb patch > separately to fb maintainers and then let's do the header move after all > those are merged as a clean-up. That avoids some dependencies between these > branches. > > Regards, > > Tony >
next prev parent reply other threads:[~2018-09-20 22:43 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-08-20 18:13 [PATCH 0/3] ARM: OMAP1: ams-delta: Clean up GPIO setup for MODEM Janusz Krzysztofik 2018-08-20 18:13 ` Janusz Krzysztofik 2018-08-20 18:13 ` [PATCH 1/3] ARM: OMAP1: ams-delta: assign MODEM IRQ from GPIO descriptor Janusz Krzysztofik 2018-08-20 18:13 ` Janusz Krzysztofik 2018-08-23 10:42 ` Linus Walleij 2018-08-23 10:42 ` Linus Walleij 2018-08-20 18:13 ` [PATCH 2/3] ARM: OMAP1: ams-delta: initialize latch2 pins to safe values Janusz Krzysztofik 2018-08-20 18:13 ` Janusz Krzysztofik 2018-08-23 10:44 ` Linus Walleij 2018-08-23 10:44 ` Linus Walleij 2018-08-20 18:13 ` [PATCH 3/3] ARM: OMAP1: ams-delta: register MODEM device earlier Janusz Krzysztofik 2018-08-20 18:13 ` Janusz Krzysztofik 2018-08-23 10:45 ` Linus Walleij 2018-08-23 10:45 ` Linus Walleij 2018-09-07 16:56 ` [PATCH 0/3] ARM: OMAP1: ams-delta: Clean up GPIO setup for MODEM Tony Lindgren 2018-09-07 16:56 ` Tony Lindgren 2018-09-09 23:44 ` [PATCH v2 " Janusz Krzysztofik 2018-09-09 23:44 ` Janusz Krzysztofik 2018-09-09 23:44 ` Janusz Krzysztofik 2018-09-09 23:44 ` [PATCH v2 1/3] ARM: OMAP1: ams-delta: assign MODEM IRQ from GPIO descriptor Janusz Krzysztofik 2018-09-09 23:44 ` Janusz Krzysztofik 2018-09-09 23:44 ` Janusz Krzysztofik 2018-09-09 23:44 ` [PATCH v2 2/3] ARM: OMAP1: ams-delta: initialize latch2 pins to safe values Janusz Krzysztofik 2018-09-09 23:44 ` Janusz Krzysztofik 2018-09-09 23:44 ` Janusz Krzysztofik 2018-09-09 23:44 ` [PATCH v2 3/3] ARM: OMAP1: ams-delta: register MODEM device earlier Janusz Krzysztofik 2018-09-09 23:44 ` Janusz Krzysztofik 2018-09-09 23:44 ` Janusz Krzysztofik 2018-09-10 21:49 ` [PATCH v2 0/3] ARM: OMAP1: ams-delta: Clean up GPIO setup for MODEM Janusz Krzysztofik 2018-09-10 21:49 ` Janusz Krzysztofik 2018-09-20 21:23 ` Tony Lindgren 2018-09-20 21:23 ` Tony Lindgren 2018-09-20 22:43 ` Janusz Krzysztofik [this message] 2018-09-20 22:43 ` Janusz Krzysztofik
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=4137539.DlEMru2qd5@z50 \ --to=jmkrzyszt@gmail.com \ --cc=aaro.koskinen@iki.fi \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=tony@atomide.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: linkBe 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.