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:44:53 +0300 [thread overview]
Message-ID: <Y1GJFakunT78fXmE@smile.fi.intel.com> (raw)
In-Reply-To: <Y1GItraKIaDqFMjG@smile.fi.intel.com>
On Thu, Oct 20, 2022 at 08:43:18PM +0300, Andy Shevchenko wrote:
> 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:
...
> > 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.
And I just realized that if any of new GPIO code will appear with the wrong
headers, there will be an inconsistent state. That said, I prefer this PR is
go as is.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-10-20 17:45 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
2022-10-20 17:44 ` Andy Shevchenko [this message]
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=Y1GJFakunT78fXmE@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;
as well as URLs for NNTP newsgroup(s).