From: Greg KH <gregkh@linuxfoundation.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
geert+renesas@glider.be, Linus Walleij <linus.walleij@linaro.org>
Subject: Re: Patch "gpio: TODO: remove the task for converting to the new line setters" has been added to the 6.17-stable tree
Date: Mon, 13 Oct 2025 15:34:01 +0200 [thread overview]
Message-ID: <2025101353-charred-squishier-6f0e@gregkh> (raw)
In-Reply-To: <CAMRc=MeD1FgCxEwSUgOJythtKU2R=6OZ0vJg0_rjhdJOneW+5w@mail.gmail.com>
On Mon, Oct 13, 2025 at 09:38:37AM +0200, Bartosz Golaszewski wrote:
> On Sun, Oct 12, 2025 at 3:57 PM Sasha Levin <sashal@kernel.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > gpio: TODO: remove the task for converting to the new line setters
> >
> > to the 6.17-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > gpio-todo-remove-the-task-for-converting-to-the-new-.patch
> > and it can be found in the queue-6.17 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
>
> As per commit message: this is neither a fix nor even a new feature,
> this is just a change in the TODO file. Please drop it, this has no
> place in stable branches.
Now dropped, thanks for the review.
greg k-h
prev parent reply other threads:[~2025-10-13 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251012135727.2876348-1-sashal@kernel.org>
2025-10-13 7:38 ` Patch "gpio: TODO: remove the task for converting to the new line setters" has been added to the 6.17-stable tree Bartosz Golaszewski
2025-10-13 13:34 ` Greg KH [this message]
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=2025101353-charred-squishier-6f0e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brgl@bgdev.pl \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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