From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
Cc: 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,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 5.10 000/111] 5.10.217-rc1 review
Date: Fri, 17 May 2024 11:22:37 +0200 [thread overview]
Message-ID: <2024051700-jubilant-rotunda-eaac@gregkh> (raw)
In-Reply-To: <ZkX+WBV4vJNpwX1i@duo.ucw.cz>
On Thu, May 16, 2024 at 02:38:48PM +0200, Pavel Machek wrote:
> Hi!
>
> > This is the start of the stable review cycle for the 5.10.217 release.
> > There are 111 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.
>
>
> > Stephen Boyd <sboyd@kernel.org>
> > clk: Don't hold prepare_lock when calling kref_put()
>
> Stephen said in a message that this depends on other patches,
> including 9d1e795f754d clk: Get runtime PM before walking tree for
> clk_summary. But we don't seem to have that one. Can you double-check?
>
> (
> Date: Tue, 23 Apr 2024 12:24:51 -0700
> Subject: Re: [PATCH AUTOSEL 5.4 6/8] clk: Don't hold prepare_lock when calling kref_put()
> )
Ugh, please use lore links when referring to other threads so that we
don't have to figure it out on our own...
Anyway, that one commit seems missing, I'll look into it.
greg k-h
next prev parent reply other threads:[~2024-05-17 9:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 10:18 [PATCH 5.10 000/111] 5.10.217-rc1 review Greg Kroah-Hartman
2024-05-14 10:20 ` [PATCH 5.10 108/111] drm/vmwgfx: Fix invalid reads in fence signaled events Greg Kroah-Hartman
2024-05-14 19:43 ` [PATCH 5.10 000/111] 5.10.217-rc1 review Pavel Machek
2024-05-15 3:17 ` Florian Fainelli
2024-05-15 10:14 ` Naresh Kamboju
2024-05-16 12:31 ` Jon Hunter
2024-05-16 12:38 ` Pavel Machek
2024-05-17 9:22 ` Greg Kroah-Hartman [this message]
2024-05-17 9:26 ` Greg Kroah-Hartman
2024-05-16 19:53 ` Shreeya Patel
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=2024051700-jubilant-rotunda-eaac@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--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