This is the start of the stable review cycle for the 6.1.38 release.
There are 13 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 Thu, 06 Jul 2023 08:46:01 +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/v6.x/stable-review/patch-6.1.38-rc2.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 6.1.38-rc2
Linus Torvalds <[email protected]>
gup: avoid stack expansion warning for known-good case
Rodrigo Siqueira <[email protected]>
drm/amd/display: Ensure vmin and vmax adjust for DCE
Bas Nieuwenhuizen <[email protected]>
drm/amdgpu: Validate VM ioctl flags.
Ahmed S. Darwish <[email protected]>
docs: Set minimal gtags / GNU GLOBAL version to 6.6.5
Ahmed S. Darwish <[email protected]>
scripts/tags.sh: Resolve gtags empty index generation
Krister Johansen <[email protected]>
perf symbols: Symbol lookup with kcore can fail if multiple segments match stext
Finn Thain <[email protected]>
nubus: Partially revert proc_create_single_data() conversion
Linus Torvalds <[email protected]>
execve: always mark stack as growing down during early stack setup
Mario Limonciello <[email protected]>
PCI/ACPI: Call _REG when transitioning D-states
Bjorn Helgaas <[email protected]>
PCI/ACPI: Validate acpi_pci_set_power_state() parameter
Aric Cyr <[email protected]>
drm/amd/display: Do not update DRR while BW optimizations pending
Alvin Lee <[email protected]>
drm/amd/display: Remove optimization for VRR updates
Max Filippov <[email protected]>
xtensa: fix lock_mm_and_find_vma in case VMA not found
-------------
Diffstat:
Documentation/process/changes.rst | 7 +++++
Makefile | 4 +--
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 +++
drivers/gpu/drm/amd/display/dc/core/dc.c | 50 +++++++++++++++++-------------
drivers/nubus/proc.c | 22 ++++++++++---
drivers/pci/pci-acpi.c | 53 ++++++++++++++++++++++++--------
include/linux/mm.h | 4 ++-
mm/memory.c | 4 +++
mm/nommu.c | 7 ++++-
scripts/tags.sh | 9 +++++-
tools/perf/util/symbol.c | 17 ++++++++--
11 files changed, 135 insertions(+), 46 deletions(-)
Hi Greg
On Tue, Jul 4, 2023 at 5:49 PM Greg Kroah-Hartman
<[email protected]> wrote:
>
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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 Thu, 06 Jul 2023 08:46:01 +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/v6.x/stable-review/patch-6.1.38-rc2.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
6.1.38-rc2 tested.
Build successfully completed.
Boot successfully completed.
No dmesg regressions.
Video output normal.
Sound output normal.
Lenovo ThinkPad X1 Carbon Gen10(Intel i7-1260P(x86_64), arch linux)
Thanks
Tested-by: Takeshi Ogasawara <[email protected]>
On Tue, Jul 04, 2023 at 09:48:32AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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.
>
Successfully compiled and installed bindeb-pkgs on my computer (Acer
Aspire E15, Intel Core i3 Haswell). No noticeable regressions.
Tested-by: Bagas Sanjaya <[email protected]>
--
An old man doll... just what I always wanted! - Clara
On Tue, Jul 04, 2023 at 09:48:32AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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.
Tested-by: Conor Dooley <[email protected]>
Cheers,
Conor.
On 7/4/23 1:48 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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 Thu, 06 Jul 2023 08:46:01 +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/v6.x/stable-review/patch-6.1.38-rc2.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Built and booted successfully on RISC-V RV64 (HiFive Unmatched).
Tested-by: Ron Economos <[email protected]>
On 7/4/23 01:48, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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 Thu, 06 Jul 2023 08:46:01 +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/v6.x/stable-review/patch-6.1.38-rc2.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
> -------------
> Pseudo-Shortlog of commits:
>
> Greg Kroah-Hartman <[email protected]>
> Linux 6.1.38-rc2
>
> Linus Torvalds <[email protected]>
> gup: avoid stack expansion warning for known-good case
>
I am a bit puzzled by this patch. It avoids a warning introduced with
upstream commit a425ac5365f6 ("gup: add warning if some caller would
seem to want stack expansion"), or at least it says so, but that patch
is not in v6.1.y. Why is this patch needed here ?
Thanks,
Guenter
> Rodrigo Siqueira <[email protected]>
> drm/amd/display: Ensure vmin and vmax adjust for DCE
>
> Bas Nieuwenhuizen <[email protected]>
> drm/amdgpu: Validate VM ioctl flags.
>
> Ahmed S. Darwish <[email protected]>
> docs: Set minimal gtags / GNU GLOBAL version to 6.6.5
>
> Ahmed S. Darwish <[email protected]>
> scripts/tags.sh: Resolve gtags empty index generation
>
> Krister Johansen <[email protected]>
> perf symbols: Symbol lookup with kcore can fail if multiple segments match stext
>
> Finn Thain <[email protected]>
> nubus: Partially revert proc_create_single_data() conversion
>
> Linus Torvalds <[email protected]>
> execve: always mark stack as growing down during early stack setup
>
> Mario Limonciello <[email protected]>
> PCI/ACPI: Call _REG when transitioning D-states
>
> Bjorn Helgaas <[email protected]>
> PCI/ACPI: Validate acpi_pci_set_power_state() parameter
>
> Aric Cyr <[email protected]>
> drm/amd/display: Do not update DRR while BW optimizations pending
>
> Alvin Lee <[email protected]>
> drm/amd/display: Remove optimization for VRR updates
>
> Max Filippov <[email protected]>
> xtensa: fix lock_mm_and_find_vma in case VMA not found
>
>
> -------------
>
> Diffstat:
>
> Documentation/process/changes.rst | 7 +++++
> Makefile | 4 +--
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 +++
> drivers/gpu/drm/amd/display/dc/core/dc.c | 50 +++++++++++++++++-------------
> drivers/nubus/proc.c | 22 ++++++++++---
> drivers/pci/pci-acpi.c | 53 ++++++++++++++++++++++++--------
> include/linux/mm.h | 4 ++-
> mm/memory.c | 4 +++
> mm/nommu.c | 7 ++++-
> scripts/tags.sh | 9 +++++-
> tools/perf/util/symbol.c | 17 ++++++++--
> 11 files changed, 135 insertions(+), 46 deletions(-)
>
>
* Greg Kroah-Hartman <[email protected]> wrote:
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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 Thu, 06 Jul 2023 08:46:01 +0000.
> Anything received after that time might be too late.
Hi Greg
6.1.38-rc2
compiles, boots and runs here on x86_64
(AMD Ryzen 5 PRO 4650G, Slackware64-15.0)
Tested-by: Markus Reichelt <[email protected]>
On 7/5/23 09:06, Greg Kroah-Hartman wrote:
> On Wed, Jul 05, 2023 at 07:23:30AM -0700, Guenter Roeck wrote:
>> On 7/4/23 01:48, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 6.1.38 release.
>>> There are 13 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 Thu, 06 Jul 2023 08:46:01 +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/v6.x/stable-review/patch-6.1.38-rc2.gz
>>> or in the git tree and branch at:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
>>> and the diffstat can be found below.
>>>
>>> thanks,
>>>
>>> greg k-h
>>>
>>> -------------
>>> Pseudo-Shortlog of commits:
>>>
>>> Greg Kroah-Hartman <[email protected]>
>>> Linux 6.1.38-rc2
>>>
>>> Linus Torvalds <[email protected]>
>>> gup: avoid stack expansion warning for known-good case
>>>
>>
>> I am a bit puzzled by this patch. It avoids a warning introduced with
>> upstream commit a425ac5365f6 ("gup: add warning if some caller would
>> seem to want stack expansion"), or at least it says so, but that patch
>> is not in v6.1.y. Why is this patch needed here ?
>
> It isn't, and was dropped for -rc2, right?
>
The above is from the -rc2 log so, no, it was not dropped. I checked in the
repository to be sure. It is also in v6.3.12-rc2 and v6.4.2-rc2, but there
it makes sense because a425ac5365f6 was applied/backported to those branches.
Thanks,
Guenter
On Wed, Jul 05, 2023 at 07:23:30AM -0700, Guenter Roeck wrote:
> On 7/4/23 01:48, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.38 release.
> > There are 13 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 Thu, 06 Jul 2023 08:46:01 +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/v6.x/stable-review/patch-6.1.38-rc2.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> >
> > -------------
> > Pseudo-Shortlog of commits:
> >
> > Greg Kroah-Hartman <[email protected]>
> > Linux 6.1.38-rc2
> >
> > Linus Torvalds <[email protected]>
> > gup: avoid stack expansion warning for known-good case
> >
>
> I am a bit puzzled by this patch. It avoids a warning introduced with
> upstream commit a425ac5365f6 ("gup: add warning if some caller would
> seem to want stack expansion"), or at least it says so, but that patch
> is not in v6.1.y. Why is this patch needed here ?
It isn't, and was dropped for -rc2, right?
thanks,
greg k-h
On Tue, Jul 04, 2023 at 09:48:32AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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 Thu, 06 Jul 2023 08:46:01 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 157 pass: 157 fail: 0
Qemu test results:
total: 519 pass: 519 fail: 0
Tested-by: Guenter Roeck <[email protected]>
Guenter
On Wed, Jul 05, 2023 at 09:13:58AM -0700, Guenter Roeck wrote:
> On 7/5/23 09:06, Greg Kroah-Hartman wrote:
> > On Wed, Jul 05, 2023 at 07:23:30AM -0700, Guenter Roeck wrote:
> > > On 7/4/23 01:48, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 6.1.38 release.
> > > > There are 13 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 Thu, 06 Jul 2023 08:46:01 +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/v6.x/stable-review/patch-6.1.38-rc2.gz
> > > > or in the git tree and branch at:
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> > > > and the diffstat can be found below.
> > > >
> > > > thanks,
> > > >
> > > > greg k-h
> > > >
> > > > -------------
> > > > Pseudo-Shortlog of commits:
> > > >
> > > > Greg Kroah-Hartman <[email protected]>
> > > > Linux 6.1.38-rc2
> > > >
> > > > Linus Torvalds <[email protected]>
> > > > gup: avoid stack expansion warning for known-good case
> > > >
> > >
> > > I am a bit puzzled by this patch. It avoids a warning introduced with
> > > upstream commit a425ac5365f6 ("gup: add warning if some caller would
> > > seem to want stack expansion"), or at least it says so, but that patch
> > > is not in v6.1.y. Why is this patch needed here ?
> >
> > It isn't, and was dropped for -rc2, right?
> >
>
> The above is from the -rc2 log so, no, it was not dropped. I checked in the
> repository to be sure. It is also in v6.3.12-rc2 and v6.4.2-rc2, but there
> it makes sense because a425ac5365f6 was applied/backported to those branches.
Ah, I must have dropped it right after the -rc2 announcement, it's been
a long week already:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=a5847f7c495fdc9c0a7b63703237f2891a6b6ed1
but be sure, it's gone from all branches now.
thanks,
greg k-h
On Wed, Jul 05, 2023 at 05:25:24PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jul 05, 2023 at 09:13:58AM -0700, Guenter Roeck wrote:
> > On 7/5/23 09:06, Greg Kroah-Hartman wrote:
> > > On Wed, Jul 05, 2023 at 07:23:30AM -0700, Guenter Roeck wrote:
> > > > On 7/4/23 01:48, Greg Kroah-Hartman wrote:
> > > > > This is the start of the stable review cycle for the 6.1.38 release.
> > > > > There are 13 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 Thu, 06 Jul 2023 08:46:01 +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/v6.x/stable-review/patch-6.1.38-rc2.gz
> > > > > or in the git tree and branch at:
> > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> > > > > and the diffstat can be found below.
> > > > >
> > > > > thanks,
> > > > >
> > > > > greg k-h
> > > > >
> > > > > -------------
> > > > > Pseudo-Shortlog of commits:
> > > > >
> > > > > Greg Kroah-Hartman <[email protected]>
> > > > > Linux 6.1.38-rc2
> > > > >
> > > > > Linus Torvalds <[email protected]>
> > > > > gup: avoid stack expansion warning for known-good case
> > > > >
> > > >
> > > > I am a bit puzzled by this patch. It avoids a warning introduced with
> > > > upstream commit a425ac5365f6 ("gup: add warning if some caller would
> > > > seem to want stack expansion"), or at least it says so, but that patch
> > > > is not in v6.1.y. Why is this patch needed here ?
> > >
> > > It isn't, and was dropped for -rc2, right?
> > >
> >
> > The above is from the -rc2 log so, no, it was not dropped. I checked in the
> > repository to be sure. It is also in v6.3.12-rc2 and v6.4.2-rc2, but there
> > it makes sense because a425ac5365f6 was applied/backported to those branches.
>
> Ah, I must have dropped it right after the -rc2 announcement, it's been
> a long week already:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=a5847f7c495fdc9c0a7b63703237f2891a6b6ed1
>
> but be sure, it's gone from all branches now.
>
Great, thanks!
Guenter
Hello!
On Tue, 04 Jul 2023 09:48:32 +0100, Greg Kroah-Hartman <[email protected]> wrote:
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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 Thu, 06 Jul 2023 08:46:01 +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/v6.x/stable-review/patch-6.1.38-rc2.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
## Build
* kernel: 6.1.38-rc2
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-6.1.y
* git commit: 185484ee4c4f93669a3a7b324d356d643fdbfe35
* git describe: v6.1.37-14-g185484ee4c4f
* test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.37-14-g185484ee4c4f
## Test Regressions (compared to v6.1.37)
No test regressions found.
## Metric Regressions (compared to v6.1.37)
No metric regressions found.
Tested-by: Linux Kernel Functional Testing <[email protected]>
## Test Fixes (compared to v6.1.37)
No test fixes found.
## Metric Fixes (compared to v6.1.37)
No metric fixes found.
## Test result summary
total: 171025, pass: 135962, fail: 2579, skip: 32314, xfail: 170
## Build Summary
* arc: 5 total, 5 passed, 0 failed
* arm: 147 total, 146 passed, 1 failed
* arm64: 53 total, 53 passed, 0 failed
* i386: 37 total, 36 passed, 1 failed
* mips: 26 total, 26 passed, 0 failed
* parisc: 3 total, 3 passed, 0 failed
* powerpc: 34 total, 34 passed, 0 failed
* riscv: 12 total, 12 passed, 0 failed
* s390: 12 total, 12 passed, 0 failed
* sh: 12 total, 12 passed, 0 failed
* sparc: 6 total, 6 passed, 0 failed
* x86_64: 42 total, 42 passed, 0 failed
## Test suites summary
* boot
* fwts
* kselftest-android
* kselftest-arm64
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers-dma-buf
* kselftest-efivarfs
* kselftest-exec
* kselftest-filesystems
* kselftest-filesystems-binderfs
* kselftest-firmware
* kselftest-fpu
* kselftest-ftrace
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kexec
* kselftest-kvm
* kselftest-lib
* kselftest-livepatch
* kselftest-membarrier
* kselftest-memfd
* kselftest-memory-hotplug
* kselftest-mincore
* kselftest-mount
* kselftest-mqueue
* kselftest-net
* kselftest-net-forwarding
* kselftest-net-mptcp
* kselftest-netfilter
* kselftest-nsfs
* kselftest-openat2
* kselftest-pid_namespace
* kselftest-pidfd
* kselftest-proc
* kselftest-pstore
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-splice
* kselftest-static_keys
* kselftest-sync
* kselftest-sysctl
* kselftest-tc-testing
* kselftest-timens
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-user_events
* kselftest-vDSO
* kselftest-watchdog
* kselftest-x86
* kselftest-zram
* kunit
* kvm-unit-tests
* libgpiod
* libhugetlbfs
* log-parser-boot
* log-parser-test
* ltp-cap_bounds
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-filecaps
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-fsx
* ltp-hugetlb
* ltp-io
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-pty
* ltp-sched
* ltp-securebits
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* network-basic-tests
* perf
* rcutorture
* v4l2-compliance
* vdso
Greetings!
Daniel Díaz
[email protected]
--
Linaro LKFT
https://lkft.linaro.org
Hello Greg,
> From: Greg Kroah-Hartman <[email protected]>
> Sent: Tuesday, July 4, 2023 9:49 AM
>
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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 Thu, 06 Jul 2023 08:46:01 +0000.
> Anything received after that time might be too late.
Thank you for the release!
CIP configurations built and booted okay with Linux 6.1.38-rc2 (185484ee4c4f):
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/920271897/
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/commits/linux-6.1.y
Tested-by: Chris Paterson (CIP) <[email protected]>
Kind regards, Chris
On Tue, 04 Jul 2023 09:48:32 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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 Thu, 06 Jul 2023 08:46:01 +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/v6.x/stable-review/patch-6.1.38-rc2.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
All tests passing for Tegra ...
Test results for stable-v6.1:
7 builds: 7 pass, 0 fail
22 boots: 22 pass, 0 fail
104 tests: 104 pass, 0 fail
Linux version: 6.1.38-rc2-g185484ee4c4f
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
tegra210-p2371-2180, tegra210-p3450-0000,
tegra30-cardhu-a04
Tested-by: Jon Hunter <[email protected]>
Jon