From: Linus Walleij <linus.walleij@linaro.org>
To: Jianqun Xu <jay.xu@rock-chips.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"Rob Herring" <robh+dt@kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8 0/9] gpio-rockchip driver
Date: Tue, 17 Aug 2021 01:04:47 +0200 [thread overview]
Message-ID: <CACRpkdaVJn9UosC5VwkQ5fTdrymtHpajc1h8HMomVS-R6vggbw@mail.gmail.com> (raw)
In-Reply-To: <20210816011948.1118959-1-jay.xu@rock-chips.com>
On Mon, Aug 16, 2021 at 3:19 AM Jianqun Xu <jay.xu@rock-chips.com> wrote:
> Separate gpio driver from pinctrl driver, and support gpio v2 controller.
I merged this into an immutable branch here:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=ib-rockchip
Then I merged that into my devel branch for v5.15.
Bartosz: pull this into the GPIO tree if you need it, e.g. if you want
to fix stuff on top.
Yours,
Linus Walleij
prev parent reply other threads:[~2021-08-16 23:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 1:19 [PATCH v8 0/9] gpio-rockchip driver Jianqun Xu
2021-08-16 1:19 ` [PATCH v8 1/9] pinctrl/rockchip: always enable clock for gpio controller Jianqun Xu
2021-08-18 19:57 ` [irqchip: irq/irqchip-next] " irqchip-bot for Jianqun Xu
2021-08-16 1:19 ` [PATCH v8 2/9] pinctrl/rockchip: separate struct rockchip_pin_bank to a head file Jianqun Xu
2021-08-18 19:57 ` [irqchip: irq/irqchip-next] " irqchip-bot for Jianqun Xu
2021-08-16 1:19 ` [PATCH v8 3/9] pinctrl/rockchip: add pinctrl device to gpio bank struct Jianqun Xu
2021-08-18 19:57 ` [irqchip: irq/irqchip-next] " irqchip-bot for Jianqun Xu
2021-08-16 1:19 ` [PATCH v8 4/9] dt-bindings: gpio: change items restriction of clock for rockchip,gpio-bank Jianqun Xu
2021-08-18 19:57 ` [irqchip: irq/irqchip-next] " irqchip-bot for Jianqun Xu
2021-08-16 1:20 ` [PATCH v8 5/9] gpio/rockchip: add driver for rockchip gpio Jianqun Xu
2021-08-18 19:57 ` [irqchip: irq/irqchip-next] " irqchip-bot for Jianqun Xu
2021-08-16 1:21 ` [PATCH v8 6/9] gpio/rockchip: use struct rockchip_gpio_regs for gpio controller Jianqun Xu
2021-08-18 19:57 ` [irqchip: irq/irqchip-next] " irqchip-bot for Jianqun Xu
2021-08-16 1:21 ` [PATCH v8 7/9] gpio/rockchip: support next version " Jianqun Xu
2021-08-18 19:56 ` [irqchip: irq/irqchip-next] " irqchip-bot for Jianqun Xu
2021-08-16 1:21 ` [PATCH v8 8/9] gpio/rockchip: drop irq_gc_lock/irq_gc_unlock for irq set type Jianqun Xu
2021-08-18 19:56 ` [irqchip: irq/irqchip-next] " irqchip-bot for Jianqun Xu
2021-08-16 1:21 ` [PATCH v8 9/9] pinctrl/rockchip: drop the gpio related codes Jianqun Xu
2021-08-18 19:56 ` [irqchip: irq/irqchip-next] " irqchip-bot for Jianqun Xu
2021-09-27 10:18 ` [PATCH v8 9/9] " Guillaume Tucker
2021-09-27 21:04 ` Heiko Stuebner
2021-08-16 19:13 ` [PATCH v8 0/9] gpio-rockchip driver Bartosz Golaszewski
2021-08-16 23:05 ` Linus Walleij
2021-08-16 23:04 ` Linus Walleij [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=CACRpkdaVJn9UosC5VwkQ5fTdrymtHpajc1h8HMomVS-R6vggbw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jay.xu@rock-chips.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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 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).