Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On 7/1/20 8:40 AM, Sasha Levin wrote: On Tue, Jun 30, 2020 at 05:33:25PM +0200, Greg Kroah-Hartman wrote: On Tue, Jun 30, 2020 at 11:12:48AM -0400, Sasha Levin wrote: On Tue, Jun 30, 2020 at 10:38:45AM +0200, Greg Kroah-Hartman wrote: > On Mon, Jun 29, 2020 at 07:18:26PM -0400, Sasha Levin wrote: > > On Mon, Jun 29, 2020 at 02:37:53PM -0600, Shuah Khan wrote: > > > Hi Sasha, > > > > > > On 6/29/20 9:13 AM, Sasha Levin wrote: > > > > > > > > This is the start of the stable review cycle for the 5.7.7 release. > > > > There are 265 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 01 Jul 2020 03:14:48 PM UTC. > > > > Anything received after that time might be too late. > > > > > > > > The whole patch series can be found in one patch at: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 > > > > > > > > > > Looks like patch naming convention has changed. My scripts look > > > for the following convention Greg uses. Are you planning to use > > > the above going forward? My scripts failed looking for the usual > > > naming convention. > > > > > > The whole patch series can be found in one patch at: > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.6-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-5.7.y > > > and the diffstat can be found below. > > > > Sorry for that. I was hoping to avoid using the signed upload mechanism > > Greg was using by simply pointing the links to automatically generated > > patches on cgit (the git.kernel.org interface). > > > > Would it be ok to change the pattern matching here? Something like this > > should work for both Greg's format and my own (and whatever may come > > next): > > > > grep -A1 "The whole patch series can be found in one patch at:" | tail -n1 | sed 's/\t//' > > If those don't work, I can still push out -rc1 patches. > > It might be best given that the above -rc.git tree is unstable and can, > and will, change, and patches stored on kernel.org will not. That's a good point. Maybe we should push tags for -rc releases too? that would allow us to keep stable links using the git.kernel.org interface. If we really want to do this, then yes, we could. But that kind of goes against what we (well I) have been doing in the past with that tree... We've been force pushing it, yes, but if we add tags it would just keep older version around so I don't think it would change much for our workflow, but it would make it easy to get to older versions. I can make changes to my scripts as long as the process is consistent for stable releases. Let mw know what you come up with, I will make adjustments to my scripts. thanks, -- Shuah
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On Tue, Jun 30, 2020 at 10:22:51AM -0700, Guenter Roeck wrote: On Mon, Jun 29, 2020 at 11:13:53AM -0400, Sasha Levin wrote: This is the start of the stable review cycle for the 5.7.7 release. There are 265 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 01 Jul 2020 03:14:48 PM UTC. Anything received after that time might be too late. Build results: total: 155 pass: 155 fail: 0 Qemu test results: total: 430 pass: 430 fail: 0 Thanks Guenter! -- Thanks, Sasha
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On Tue, Jun 30, 2020 at 10:15:31AM +0100, Jon Hunter wrote: On 29/06/2020 16:13, Sasha Levin wrote: This is the start of the stable review cycle for the 5.7.7 release. There are 265 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 01 Jul 2020 03:14:48 PM UTC. Anything received after that time might be too late. The whole patch series can be found in one patch at: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.7.y and the diffstat can be found below. -- Thanks, Sasha All tests are passing for Tegra ... Test results for stable-v5.7: 11 builds: 11 pass, 0 fail 26 boots:26 pass, 0 fail 56 tests:56 pass, 0 fail Linux version: 5.7.7-rc1-g97943c6d41ef Boards tested: tegra124-jetson-tk1, tegra186-p2771-, tegra194-p2972-, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-, tegra30-cardhu-a04 Thanks for the testing Jon! -- Thanks, Sasha
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On Tue, Jun 30, 2020 at 10:44:12AM +0530, Naresh Kamboju wrote: On Mon, 29 Jun 2020 at 20:48, Sasha Levin wrote: This is the start of the stable review cycle for the 5.7.7 release. There are 265 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 01 Jul 2020 03:14:48 PM UTC. Anything received after that time might be too late. The whole patch series can be found in one patch at: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.7.y and the diffstat can be found below. -- Thanks, Sasha Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Thanks for testing! -- Thanks, Sasha
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On Tue, Jun 30, 2020 at 05:33:25PM +0200, Greg Kroah-Hartman wrote: On Tue, Jun 30, 2020 at 11:12:48AM -0400, Sasha Levin wrote: On Tue, Jun 30, 2020 at 10:38:45AM +0200, Greg Kroah-Hartman wrote: > On Mon, Jun 29, 2020 at 07:18:26PM -0400, Sasha Levin wrote: > > On Mon, Jun 29, 2020 at 02:37:53PM -0600, Shuah Khan wrote: > > > Hi Sasha, > > > > > > On 6/29/20 9:13 AM, Sasha Levin wrote: > > > > > > > > This is the start of the stable review cycle for the 5.7.7 release. > > > > There are 265 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 01 Jul 2020 03:14:48 PM UTC. > > > > Anything received after that time might be too late. > > > > > > > > The whole patch series can be found in one patch at: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 > > > > > > > > > > Looks like patch naming convention has changed. My scripts look > > > for the following convention Greg uses. Are you planning to use > > > the above going forward? My scripts failed looking for the usual > > > naming convention. > > > > > > The whole patch series can be found in one patch at: > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.6-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-5.7.y > > > and the diffstat can be found below. > > > > Sorry for that. I was hoping to avoid using the signed upload mechanism > > Greg was using by simply pointing the links to automatically generated > > patches on cgit (the git.kernel.org interface). > > > > Would it be ok to change the pattern matching here? Something like this > > should work for both Greg's format and my own (and whatever may come > > next): > > > > grep -A1 "The whole patch series can be found in one patch at:" | tail -n1 | sed 's/\t//' > > If those don't work, I can still push out -rc1 patches. > > It might be best given that the above -rc.git tree is unstable and can, > and will, change, and patches stored on kernel.org will not. That's a good point. Maybe we should push tags for -rc releases too? that would allow us to keep stable links using the git.kernel.org interface. If we really want to do this, then yes, we could. But that kind of goes against what we (well I) have been doing in the past with that tree... We've been force pushing it, yes, but if we add tags it would just keep older version around so I don't think it would change much for our workflow, but it would make it easy to get to older versions. -- Thanks, Sasha
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On Mon, Jun 29, 2020 at 11:13:53AM -0400, Sasha Levin wrote: > > This is the start of the stable review cycle for the 5.7.7 release. > There are 265 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 01 Jul 2020 03:14:48 PM UTC. > Anything received after that time might be too late. > Build results: total: 155 pass: 155 fail: 0 Qemu test results: total: 430 pass: 430 fail: 0 Guenter
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On Tue, Jun 30, 2020 at 11:12:48AM -0400, Sasha Levin wrote: > On Tue, Jun 30, 2020 at 10:38:45AM +0200, Greg Kroah-Hartman wrote: > > On Mon, Jun 29, 2020 at 07:18:26PM -0400, Sasha Levin wrote: > > > On Mon, Jun 29, 2020 at 02:37:53PM -0600, Shuah Khan wrote: > > > > Hi Sasha, > > > > > > > > On 6/29/20 9:13 AM, Sasha Levin wrote: > > > > > > > > > > This is the start of the stable review cycle for the 5.7.7 release. > > > > > There are 265 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 01 Jul 2020 03:14:48 PM UTC. > > > > > Anything received after that time might be too late. > > > > > > > > > > The whole patch series can be found in one patch at: > > > > > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 > > > > > > > > > > > > > Looks like patch naming convention has changed. My scripts look > > > > for the following convention Greg uses. Are you planning to use > > > > the above going forward? My scripts failed looking for the usual > > > > naming convention. > > > > > > > > The whole patch series can be found in one patch at: > > > > > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.6-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-5.7.y > > > > and the diffstat can be found below. > > > > > > Sorry for that. I was hoping to avoid using the signed upload mechanism > > > Greg was using by simply pointing the links to automatically generated > > > patches on cgit (the git.kernel.org interface). > > > > > > Would it be ok to change the pattern matching here? Something like this > > > should work for both Greg's format and my own (and whatever may come > > > next): > > > > > > grep -A1 "The whole patch series can be found in one patch at:" | tail > > > -n1 | sed 's/\t//' > > > > If those don't work, I can still push out -rc1 patches. > > > > It might be best given that the above -rc.git tree is unstable and can, > > and will, change, and patches stored on kernel.org will not. > > That's a good point. Maybe we should push tags for -rc releases too? > that would allow us to keep stable links using the git.kernel.org > interface. If we really want to do this, then yes, we could. But that kind of goes against what we (well I) have been doing in the past with that tree... thanks, greg k-h
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
Hello! On Tue, 30 Jun 2020 at 10:12, Sasha Levin wrote: > > On Tue, Jun 30, 2020 at 10:38:45AM +0200, Greg Kroah-Hartman wrote: > >On Mon, Jun 29, 2020 at 07:18:26PM -0400, Sasha Levin wrote: > >> On Mon, Jun 29, 2020 at 02:37:53PM -0600, Shuah Khan wrote: > >> > Hi Sasha, > >> > > >> > On 6/29/20 9:13 AM, Sasha Levin wrote: > >> > > > >> > > This is the start of the stable review cycle for the 5.7.7 release. > >> > > There are 265 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 01 Jul 2020 03:14:48 PM UTC. > >> > > Anything received after that time might be too late. > >> > > > >> > > The whole patch series can be found in one patch at: > >> > > > >> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 > >> > > > >> > > >> > Looks like patch naming convention has changed. My scripts look > >> > for the following convention Greg uses. Are you planning to use > >> > the above going forward? My scripts failed looking for the usual > >> > naming convention. > >> > > >> > The whole patch series can be found in one patch at: > >> > > >> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.6-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-5.7.y > >> > and the diffstat can be found below. > >> > >> Sorry for that. I was hoping to avoid using the signed upload mechanism > >> Greg was using by simply pointing the links to automatically generated > >> patches on cgit (the git.kernel.org interface). > >> > >> Would it be ok to change the pattern matching here? Something like this > >> should work for both Greg's format and my own (and whatever may come > >> next): > >> > >> grep -A1 "The whole patch series can be found in one patch at:" | > >> tail -n1 | sed 's/\t//' > > > >If those don't work, I can still push out -rc1 patches. > > > >It might be best given that the above -rc.git tree is unstable and can, > >and will, change, and patches stored on kernel.org will not. > > That's a good point. Maybe we should push tags for -rc releases too? That would be GREAT for those CI's or processes looking for a definite trigger to use. Greetings! Daniel Díaz daniel.d...@linaro.org
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On Tue, Jun 30, 2020 at 10:38:45AM +0200, Greg Kroah-Hartman wrote: On Mon, Jun 29, 2020 at 07:18:26PM -0400, Sasha Levin wrote: On Mon, Jun 29, 2020 at 02:37:53PM -0600, Shuah Khan wrote: > Hi Sasha, > > On 6/29/20 9:13 AM, Sasha Levin wrote: > > > > This is the start of the stable review cycle for the 5.7.7 release. > > There are 265 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 01 Jul 2020 03:14:48 PM UTC. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 > > > > Looks like patch naming convention has changed. My scripts look > for the following convention Greg uses. Are you planning to use > the above going forward? My scripts failed looking for the usual > naming convention. > > The whole patch series can be found in one patch at: > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.6-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-5.7.y > and the diffstat can be found below. Sorry for that. I was hoping to avoid using the signed upload mechanism Greg was using by simply pointing the links to automatically generated patches on cgit (the git.kernel.org interface). Would it be ok to change the pattern matching here? Something like this should work for both Greg's format and my own (and whatever may come next): grep -A1 "The whole patch series can be found in one patch at:" | tail -n1 | sed 's/\t//' If those don't work, I can still push out -rc1 patches. It might be best given that the above -rc.git tree is unstable and can, and will, change, and patches stored on kernel.org will not. That's a good point. Maybe we should push tags for -rc releases too? that would allow us to keep stable links using the git.kernel.org interface. -- Thanks, Sasha
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On 29/06/2020 16:13, Sasha Levin wrote: > > This is the start of the stable review cycle for the 5.7.7 release. > There are 265 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 01 Jul 2020 03:14:48 PM UTC. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-5.7.y > and the diffstat can be found below. > > -- > Thanks, > Sasha All tests are passing for Tegra ... Test results for stable-v5.7: 11 builds: 11 pass, 0 fail 26 boots: 26 pass, 0 fail 56 tests: 56 pass, 0 fail Linux version: 5.7.7-rc1-g97943c6d41ef Boards tested: tegra124-jetson-tk1, tegra186-p2771-, tegra194-p2972-, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-, tegra30-cardhu-a04 Cheers Jon -- nvpublic
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On Mon, Jun 29, 2020 at 07:18:26PM -0400, Sasha Levin wrote: > On Mon, Jun 29, 2020 at 02:37:53PM -0600, Shuah Khan wrote: > > Hi Sasha, > > > > On 6/29/20 9:13 AM, Sasha Levin wrote: > > > > > > This is the start of the stable review cycle for the 5.7.7 release. > > > There are 265 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 01 Jul 2020 03:14:48 PM UTC. > > > Anything received after that time might be too late. > > > > > > The whole patch series can be found in one patch at: > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 > > > > > > > Looks like patch naming convention has changed. My scripts look > > for the following convention Greg uses. Are you planning to use > > the above going forward? My scripts failed looking for the usual > > naming convention. > > > > The whole patch series can be found in one patch at: > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.6-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-5.7.y > > and the diffstat can be found below. > > Sorry for that. I was hoping to avoid using the signed upload mechanism > Greg was using by simply pointing the links to automatically generated > patches on cgit (the git.kernel.org interface). > > Would it be ok to change the pattern matching here? Something like this > should work for both Greg's format and my own (and whatever may come > next): > > grep -A1 "The whole patch series can be found in one patch at:" | tail > -n1 | sed 's/\t//' If those don't work, I can still push out -rc1 patches. It might be best given that the above -rc.git tree is unstable and can, and will, change, and patches stored on kernel.org will not. thanks, greg k-h
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On Mon, 29 Jun 2020 at 20:48, Sasha Levin wrote: > > > This is the start of the stable review cycle for the 5.7.7 release. > There are 265 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 01 Jul 2020 03:14:48 PM UTC. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-5.7.y > and the diffstat can be found below. > > -- > Thanks, > Sasha Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Summary kernel: 5.7.7-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.7.y git commit: 97943c6d41ef2b05f4e064eb49a538ff4b405809 git describe: v5.7.6-265-g97943c6d41ef Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.7-oe/build/v5.7.6-265-g97943c6d41ef No regressions (compared to build v5.7.6) No fixes (compared to build v5.7.6) Ran 36511 total tests in the following environments and test suites. Environments -- - dragonboard-410c - hi6220-hikey - i386 - juno-r2 - juno-r2-compat - juno-r2-kasan - nxp-ls2088 - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64 - x15 - x86 - x86-kasan Test Suites --- * build * install-android-platform-tools-r2600 * install-android-platform-tools-r2800 * kselftest * kselftest/drivers * kselftest/filesystems * kselftest/net * libhugetlbfs * linux-log-parser * ltp-containers-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-mm-tests * ltp-sched-tests * ltp-syscalls-tests * perf * v4l2-compliance * kvm-unit-tests * ltp-cap_bounds-tests * ltp-commands-tests * ltp-cpuhotplug-tests * ltp-crypto-tests * ltp-math-tests * network-basic-tests * ltp-controllers-tests * ltp-nptl-tests * ltp-open-posix-tests * ltp-pty-tests * ltp-securebits-tests * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-native/drivers * kselftest-vsyscall-mode-native/filesystems * kselftest-vsyscall-mode-native/net * kselftest-vsyscall-mode-none * kselftest-vsyscall-mode-none/drivers * kselftest-vsyscall-mode-none/filesystems * kselftest-vsyscall-mode-none/net -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
On Mon, Jun 29, 2020 at 02:37:53PM -0600, Shuah Khan wrote: Hi Sasha, On 6/29/20 9:13 AM, Sasha Levin wrote: This is the start of the stable review cycle for the 5.7.7 release. There are 265 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 01 Jul 2020 03:14:48 PM UTC. Anything received after that time might be too late. The whole patch series can be found in one patch at: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 Looks like patch naming convention has changed. My scripts look for the following convention Greg uses. Are you planning to use the above going forward? My scripts failed looking for the usual naming convention. The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.6-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-5.7.y and the diffstat can be found below. Sorry for that. I was hoping to avoid using the signed upload mechanism Greg was using by simply pointing the links to automatically generated patches on cgit (the git.kernel.org interface). Would it be ok to change the pattern matching here? Something like this should work for both Greg's format and my own (and whatever may come next): grep -A1 "The whole patch series can be found in one patch at:" | tail -n1 | sed 's/\t//' -- Thanks, Sasha
Re: [PATCH 5.7 000/265] 5.7.7-rc1 review
Hi Sasha, On 6/29/20 9:13 AM, Sasha Levin wrote: This is the start of the stable review cycle for the 5.7.7 release. There are 265 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 01 Jul 2020 03:14:48 PM UTC. Anything received after that time might be too late. The whole patch series can be found in one patch at: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.7.y=v5.7.6 Looks like patch naming convention has changed. My scripts look for the following convention Greg uses. Are you planning to use the above going forward? My scripts failed looking for the usual naming convention. The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.6-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-5.7.y and the diffstat can be found below. thanks, -- Shuah
