From: Andy Shevchenko <andy@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Support Opensource <support.opensource@diasemi.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 0/3] pinctrl: da9062: don't pull in internal GPIOLIB headers
Date: Fri, 1 Sep 2023 15:15:09 +0300 [thread overview]
Message-ID: <ZPHVzRPvstmnIyQj@smile.fi.intel.com> (raw)
In-Reply-To: <20230901112926.13216-1-brgl@bgdev.pl>
On Fri, Sep 01, 2023 at 01:29:23PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.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().
Reviewed-by: Andy Shevchenko <andy@kernel.org>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-09-01 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 11:29 [PATCH 0/3] pinctrl: da9062: don't pull in internal GPIOLIB headers Bartosz Golaszewski
2023-09-01 11:29 ` [PATCH 1/3] pinctrl: da9062: add missing include Bartosz Golaszewski
2023-09-12 7:29 ` Linus Walleij
2023-09-12 7:45 ` Bartosz Golaszewski
2023-09-01 11:29 ` [PATCH 2/3] gpiolib: make gpiochip_get_desc() public Bartosz Golaszewski
2023-09-01 11:29 ` [PATCH 3/3] pinctrl: da9062: don't include private GPIOLIB header Bartosz Golaszewski
2023-09-01 12:15 ` Andy Shevchenko [this message]
2023-09-11 7:18 ` [PATCH 0/3] pinctrl: da9062: don't pull in internal GPIOLIB headers Bartosz Golaszewski
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=ZPHVzRPvstmnIyQj@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=support.opensource@diasemi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.