From: Sekhar Nori <nsekhar@ti.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Kevin Hilman <khilman@kernel.org>,
Russell King <linux@armlinux.org.uk>, Keerthy <j-keerthy@ti.com>,
Linus Walleij <linus.walleij@linaro.org>,
Grygorii Strashko <grygorii.strashko@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH 00/12] ARM: davinci: fix GPIO breakage after v4.19
Date: Tue, 27 Nov 2018 17:50:19 +0530 [thread overview]
Message-ID: <6eb91ecb-47b1-8f77-afcc-9ace3cb15b82@ti.com> (raw)
In-Reply-To: <20181121093523.12503-1-brgl@bgdev.pl>
Hi Bartosz,
On 21/11/18 3:05 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> This is the entire set of changes needed to fix the broken GPIO support
> for DaVinci boards in legacy mode after certain changes made to the
> GPIO driver in 4.19, namely: commits 587f7a694f01 ("gpio: davinci: Use
> dev name for label and automatic base selection") and eb3744a2dd01
> ("gpio: davinci: Do not assume continuous IRQ numbering").
I applied this series and sent a pull request to ARM SoC too.
Thanks,
Sekhar
prev parent reply other threads:[~2018-11-27 12:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 9:35 [PATCH 00/12] ARM: davinci: fix GPIO breakage after v4.19 Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 01/12] ARM: davinci: da8xx: define gpio interrupts as separate resources Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 02/12] ARM: davinci: dm365: " Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 03/12] ARM: davinci: dm646x: " Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 04/12] ARM: davinci: dm355: " Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 05/12] ARM: davinci: dm644x: " Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 06/12] gpio: davinci: restore a way to manually specify the GPIO base Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 07/12] ARM: davinci: da850: set the GPIO base to 0 Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 08/12] ARM: davinci: dm365: " Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 09/12] ARM: davinci: dm646x: " Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 10/12] ARM: davinci: dm355: " Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 11/12] ARM: davinci: da830: " Bartosz Golaszewski
2018-11-21 9:35 ` [PATCH 12/12] ARM: davinci: dm644x: " Bartosz Golaszewski
2018-11-27 12:20 ` Sekhar Nori [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=6eb91ecb-47b1-8f77-afcc-9ace3cb15b82@ti.com \
--to=nsekhar@ti.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=grygorii.strashko@ti.com \
--cc=j-keerthy@ti.com \
--cc=khilman@kernel.org \
--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@armlinux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).