Hi Pavel,
From: stable-owner@vger.kernel.org stable-owner@vger.kernel.org On Behalf Of Pavel Machek Sent: 04 August 2020 08:46
*** gpg4o | The signature of this email could not be verified because the following public key is missing. Click here to search and import the key 30E7F06A95DBFAF2 ***
Hi!
This is the start of the stable review cycle for the 4.19.137 release. There are 56 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.
Responses should be made by Wed, 05 Aug 2020 12:18:33 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v4.x/stable-
review/patch-4.19.137-rc1.gz
or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-
rc.git linux-4.19.y
and the diffstat can be found below.
CIP test farm does not see any problems...
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/- /pipelines/173700523
...except that one of the targets is unavailable.
This is up again now so I've rescheduled the tests.
Chris, could we get distinction between "we ran a test and it failed" and "we could not run a test because mice ate the cables"?
You can see that the board is offline in the GitLab CI log, but that's not ideal. I can change it so the job passes with a nice big green tick, but this may lead people to think that the tests had actually been run. Maybe we need a yellow icon in the GitLab GUI for this circumstance. Looks like we aren't the first with this request: https://gitlab.com/gitlab-org/gitlab/-/issues/16733
Kind regards, Chris
Best regards, Pavel
-- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html