[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMRc=Mcx8kUHHNY0TMMvTTa5dev5Ua7W09z8UtkTbU=+iQJu0w@mail.gmail.com>
Date: Mon, 11 Sep 2023 09:18:40 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Support Opensource <support.opensource@...semi.com>,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Andy Shevchenko <andy@...nel.org>,
Bartosz Golaszewski <brgl@...ev.pl>
Subject: Re: [PATCH 0/3] pinctrl: da9062: don't pull in internal GPIOLIB headers
On Fri, Sep 1, 2023 at 1:29 PM Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
>
> I'm removing instances of users of internal GPIOLIB headers which should
> not be included by anyone but GPIO core code. The pinctrl-da9062 driver
> uses gpiochip_get_desc() which we should put into the gpio/driver.h
> header as it does sometimes make sense for GPIO providers to get its own
> descriptors without having to go through gpiochip_request_own_desc().
>
> Bartosz Golaszewski (3):
> pinctrl: da9062: add missing include
> gpiolib: make gpiochip_get_desc() public
> pinctrl: da9062: don't include private GPIOLIB header
>
> drivers/gpio/gpiolib.h | 2 --
> drivers/pinctrl/pinctrl-da9062.c | 7 +------
> include/linux/gpio/driver.h | 2 ++
> 3 files changed, 3 insertions(+), 8 deletions(-)
>
> --
> 2.39.2
>
Linus,
Do you mind me taking these through the GPIO tree or do you prefer to
apply them yourself in which case I'll apply patch 2/3 first and
provide you with an immutable tag?
Bartosz
Powered by blists - more mailing lists