[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YUgVfJFQQhMnUWfF@kroah.com>
Date: Mon, 20 Sep 2021 07:00:44 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Alexey Khoroshilov <khoroshilov@...ras.ru>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Kevin Hao <haokexin@...il.com>,
Viresh Kumar <viresh.kumar@...aro.org>
Subject: Re: [PATCH 5.10 033/306] cpufreq: schedutil: Use kobject release()
method to free sugov_tunables
On Sun, Sep 19, 2021 at 09:36:20PM +0300, Alexey Khoroshilov wrote:
> Hi Greg,
>
> I am trying to get familiar with stable release process, because we
> would like to start testing stable release candidates. But I cannot get
> all the nuances how to get automatically information regarding rc code
> ready to be tested.
You might want to start a new thread and not bury it down in a response
to a specific commit in order to make sure that people see it.
What specifically have you tried that did not work for detecting the -rc
releases?
> Also I wonder how we could automatically detect situations when stable
> release is expected to became diverged from the rc, e.g. like
> [PATCH 5.10 033/306] cpufreq: schedutil: Use kobject release() method to
> free sugov_tunables
> was dropped from 5.10.67 without announcing the 5.10.67-rc2?
Look at the stable queue tree, that has all of the information in it,
right?
thanks,
greg k-h
Powered by blists - more mailing lists