[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdYU0qsNf=AonKR6MZg_oPNXkFnX7f2n9K4oZRBFDdtRow@mail.gmail.com>
Date: Wed, 14 Apr 2021 09:29:08 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Peter Geis <pgwipeout@...il.com>
Cc: Jianqun Xu <jay.xu@...k-chips.com>,
Tao Huang <huangtao@...k-chips.com>,
Kever Yang <kever.yang@...k-chips.com>,
Heiko Stübner <heiko@...ech.de>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/7] gpio-rockchip driver
On Sun, Apr 11, 2021 at 3:30 PM Peter Geis <pgwipeout@...il.com> wrote:
> Separate gpio driver from pinctrl driver, and support v2 controller.
>
> Tested on rk3566-quartz64 prototype board.
>
> Patch History:
> V2 - Rebase to latest linux-next.
>
> Tested-by: Peter Geis <pgwipeout@...il.com>
This does not apply to the pin control tree, the problem with basing stuff
on -next is that it sometimes does not apply to any development tree
and now that happened (because of conflicts in the GPIO tree).
You can either resend this based on the pinctrl "devel" branch:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=devel
... or you can wait until kernel v5.13-rc1 is out and then we can merge
it, but it might even require rebasing after that.
Yours,
Linus Walleij
Powered by blists - more mailing lists