From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linux pin control <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [GIT PULL] intel-pinctrl for 6.1-1
Date: Thu, 20 Oct 2022 20:43:18 +0300 [thread overview]
Message-ID: <Y1GItraKIaDqFMjG@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=Medt_M0h+1TdtRnu=7v1NmGePqfFBS02+zceXGLQ4OV3w@mail.gmail.com>
On Thu, Oct 20, 2022 at 07:31:23PM +0200, Bartosz Golaszewski wrote:
> On Thu, Oct 20, 2022 at 4:58 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > Hi Linux pin control maintainers,
> >
> > A bunch of cleanups of the pin control and GPIO headers. It has been a couple
> > of days in Linux Next without any major issue reported, a few fixes are already
> > incorporated in the respective patches. The idea is that pin control and GPIO
> > subsystems take it now and we will continue from this for all new code.
> >
> > Linus, Bart, please pull to your trees.
> > The tag is signed and can be considered as immutable.
> >
> > Thanks,
> >
> > With Best Regards,
> > Andy Shevchenko
> >
> > The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
> >
> > Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git tags/intel-pinctrl-v6.1-1
> >
> > for you to fetch changes up to 1053f6a58766ac8eadcb72630262a5a454048479:
> >
> > pinctrl: Clean up headers (2022-10-19 18:08:45 +0300)
> >
> > ----------------------------------------------------------------
> > intel-pinctrl for v6.1-1
> >
> > * Add missing and remove unused headers in pin control and GPIO drivers
> > * Revise the pin control and GPIO headers
> >
> > ----------------------------------------------------------------
> > Andy Shevchenko (50):
> > gpio: aspeed: Add missing header(s)
> > gpio: arizona: Remove unused header(s)
> > gpio: da9052: Remove unused header(s)
> > gpio: mockup: Add missing header(s)
> > gpio: pca953x: Add missing header(s)
> > gpio: pl061: Add missing header(s)
> > gpio: reg: Add missing header(s)
> > gpio: wm8350: Remove unused header(s)
> > gpio: tegra186: Add missing header(s)
> > gpiolib: cdev: Add missing header(s)
> > gpiolib: Clean up headers
>
> Can you send the GPIO changes separately? This way I don't need to
> pull all those pinctrl patches into the GPIO PR for the next merge
> window.
Some of them, but not all, if that what you wish.
I.o.w. a couple of the GPIO changes must be part of pin control series.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-10-20 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 14:49 [GIT PULL] intel-pinctrl for 6.1-1 Andy Shevchenko
2022-10-20 17:31 ` Bartosz Golaszewski
2022-10-20 17:43 ` Andy Shevchenko [this message]
2022-10-20 17:44 ` Andy Shevchenko
2022-10-21 8:02 ` Linus Walleij
2022-10-23 20:04 ` Andy Shevchenko
2022-10-24 7:16 ` Linus Walleij
2022-10-24 15:06 ` Andy Shevchenko
2022-10-25 13:34 ` Andy Shevchenko
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=Y1GItraKIaDqFMjG@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox