Received-SPF: pass (google.com: domain of linux-kernel+bounces-181923-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Date: Fri, 17 May 2024 11:26:25 +0200
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
Message-ID: <2024051744-refinery-galore-0089@gregkh>
References: <20240514100957.114746054@linuxfoundation.org>
 <ZkX+WBV4vJNpwX1i@duo.ucw.cz>
 <2024051700-jubilant-rotunda-eaac@gregkh>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2024051700-jubilant-rotunda-eaac@gregkh>

On Fri, May 17, 2024 at 11:22:37AM +0200, Greg Kroah-Hartman wrote:
> 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.

And I know you mean well, but if you had looked at it, you would have
seen that that commit isn't relevant at all to this kernel branch, which
is why it is not there.

Please be more careful with your reviews.

greg k-h