public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: Mark Brown <broonie@kernel.org>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, hargar@microsoft.com,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 6.13 000/138] 6.13.5-rc1 review
Date: Tue, 25 Feb 2025 07:46:09 +0100	[thread overview]
Message-ID: <2025022548-swiftness-supervise-ae80@gregkh> (raw)
In-Reply-To: <CACMJSeuQkzvi5j975bbb6gF=+NMz0Aw-X5xLXR=8rMUjeQUoZg@mail.gmail.com>

On Mon, Feb 24, 2025 at 08:57:10PM +0100, Bartosz Golaszewski wrote:
> On Mon, 24 Feb 2025 at 20:52, Mark Brown <broonie@kernel.org> wrote:
> >
> > On Mon, Feb 24, 2025 at 03:33:50PM +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 6.13.5 release.
> > > There are 138 patches in this series, all will be posted as a response
> > > to this one.  If anyone has any issues with these being applied, please
> > > let me know.
> >
> > This and 6.12 are broken on several platforms by "gpiolib: check the
> > return value of gpio_chip::get_direction()", as reported upstream
> > several drivers break the expectations that this commit has.
> > 96fa9ec477ff60bed87e1441fd43e003179f3253 "gpiolib: don't bail out if
> > get_direction() fails in gpiochip_add_data()" was merged upstream which
> > makes this non-fatal, but it's probably as well to just not backport
> > this to stable at all.
> 
> Agreed, this can be dropped. It never worked before so it's not a
> regression fix.

Ok, thanks, I'll drop it from all stable queues and push out some new
-rc2 releases.

greg k-h

  reply	other threads:[~2025-02-25  6:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 14:33 [PATCH 6.13 000/138] 6.13.5-rc1 review Greg Kroah-Hartman
2025-02-24 18:22 ` Florian Fainelli
2025-02-24 19:52 ` Mark Brown
2025-02-24 19:57   ` Bartosz Golaszewski
2025-02-25  6:46     ` Greg Kroah-Hartman [this message]
2025-02-25  7:29       ` Bartosz Golaszewski
2025-02-24 21:09 ` Pavel Machek
2025-02-24 21:19 ` Peter Schneider
2025-02-24 23:29 ` Shuah Khan
2025-02-25  0:03 ` Jon Hunter
2025-02-25  6:16 ` Ron Economos
  -- strict thread matches above, loose matches on Subject: below --
2025-02-24 15:16 Ronald Warsow

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=2025022548-swiftness-supervise-ae80@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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