[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMRc=Md+5N_u0QkL+OTc2xVQuxP0dZY-1GbrdGQqwhdJrv4Cbg@mail.gmail.com>
Date: Fri, 24 Nov 2023 20:40:10 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH 0/3] pinctrl: don't use gpiod_to_chip()
On Fri, Nov 24, 2023 at 11:01 AM Linus Walleij <linus.walleij@...aro.org> wrote:
>
> On Mon, Nov 20, 2023 at 4:06 PM Bartosz Golaszewski <brgl@...ev.pl> wrote:
> > On Thu, Nov 16, 2023 at 2:43 PM Linus Walleij <linus.walleij@...aro.org> wrote:
> > > On Wed, Nov 15, 2023 at 5:50 PM Bartosz Golaszewski <brgl@...ev.pl> wrote:
> > >
> > > > From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> > > >
> > > > Let's start working towards removing gpiod_to_chip() from the kernel.
> > > > Start with pinctrl. The first patch should go through the GPIO tree
> > > > and become available through an immutable tag so that we can get more
> > > > conversions in this cycle elsewhere.
> > >
> > > Fair enough, maybe an immutable branch with all three patches?
> > > Probably best to merga all three into both subsystems I think.
> > >
> >
> > Nah, I don't think I need to pollute the GPIO tree with every pinctrl
> > patch. It's enough to just merge the first one into GPIO and you do
> > the same in pinctrl.
>
> Fair enough, but I need that immutable branch for patch 1 so I
> can merge the rest on top.
>
> Yours,
> Linus Walleij
I applied the first patch (after fixing the typo in the commit
message) and sent you the immutable branch to pull. Please apply the
remaining patches to the pinctrl tree directly.
Thanks!
Bart
Powered by blists - more mailing lists