On Wed, Jun 03, 2020 at 01:21:35PM -0700, Guenter Roeck wrote:
> Hi,
>
> Please consider applying the following patches to the listed stable
> releases.
>
> The following patches were found to be missing in stable releases by the
> Chrome OS missing patch robot. The patches meet the following criteria.
> - The patch includes a Fixes: tag
> Note that the Fixes: tag does not always point to the correct upstream
> SHA. In that case the correct upstream SHA is listed below.
> - The patch referenced in the Fixes: tag has been applied to the listed
> stable release
> - The patch has not been applied to that stable release
>
> All patches have been applied to the listed stable releases and to at least
> one Chrome OS branch. Resulting images have been build- and runtime-tested
> (where applicable) on real hardware and with virtual hardware on
> kerneltests.org.
>
> Thanks,
> Guenter
>
> ---
> Upstream commit 0e0bf1ea1147 ("perf stat: Zero all the 'ena' and 'run' array slot stats for interval mode")
> upstream: ToT
> Fixes: 51fd2df1e882 ("perf stat: Fix interval output values")
> in linux-4.4.y: 7629c7ef5291
> upstream: v4.5-rc4
> Affected branches:
> linux-4.4.y
> linux-4.9.y
> linux-4.14.y
> linux-4.19.y
> linux-5.4.y
> linux-5.6.y
> Presumably also linux-5.7.y but not checked/tested
You are starting to catch patches that are now in Linus's tree, but have
not shown up in a -rc release yet. We really should wait for these
until they do show up in a real release, unless there is a specific need
otherwise.
Usually I require the maintainer of the subsystem to ask me to merge
those patches, as it gives me someone to blame if things go wrong :)
So can you hold off on these types of patches until they show up in a
-rc release?
thanks,
greg k-h
