From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Linus Walleij" <linus.walleij@linaro.org>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-input@vger.kernel.org,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Subject: Re: [GIT PULL] intel-gpio for 6.3-1
Date: Tue, 07 Mar 2023 09:09:11 +0100 [thread overview]
Message-ID: <e4cdd1f9-fc79-4f91-a4df-ab5f5a94faa3@app.fastmail.com> (raw)
In-Reply-To: <ZAZqy+LFkZuj+T4P@surfacebook>
On Mon, Mar 6, 2023, at 23:35, andy.shevchenko@gmail.com wrote:
> Mon, Mar 06, 2023 at 10:50:40PM +0100, Linus Walleij kirjoitti:
>> On Mon, Mar 6, 2023 at 4:14 PM Andy Shevchenko
>> <andriy.shevchenko@linux.intel.com> wrote:
>>
>> > Hi Linux GPIO maintainers et al.,
>> >
>> > Combined series to clean up headers in the GPIO library and drivers.
>> > Along with it, drop a few unused legacy APIs.
>> >
>> > This tag is immutable, enjoy!
>>
>> Thanks for coordinating and getting this sorted and tested Andy, perfect
>> job as always!
>
> You're welcome!
>
>> > intel-gpio for v6.3-1
>>
>> But I think you mean it for v6.4?
>
> Well, techically speaking it didn't make v6.3-rc1 due to cross-dependencies.
> Starting from it it may be applied to v6.3 or to v6.4.
>
> Up to you and Bart, but I prefer not to rebrand the tag, if it's an option.
I think it was clear that this would not make it into 6.3 after
the decision to rebase on top of 6.3-rc1. However, the tag name
and description both look like they make sense for 6.4 the way
you wrote them.
Arnd
next prev parent reply other threads:[~2023-03-07 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 15:09 [GIT PULL] intel-gpio for 6.3-1 Andy Shevchenko
2023-03-06 21:50 ` Linus Walleij
2023-03-06 22:35 ` andy.shevchenko
2023-03-07 8:09 ` Arnd Bergmann [this message]
2023-03-07 9:51 ` Andy Shevchenko
2023-03-07 11:42 ` Andy Shevchenko
2023-03-08 10:03 ` 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=e4cdd1f9-fc79-4f91-a4df-ab5f5a94faa3@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=dmitry.torokhov@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
/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).