linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 4.19 00/49] 4.19.269-rc1 review
Date: Tue, 13 Dec 2022 20:27:50 +0100	[thread overview]
Message-ID: <0f674e79-5832-d296-4db2-ec9b0c40a298@benettiengineering.com> (raw)
In-Reply-To: <CA+G9fYtCTQHiW_pr+M8AVrLn-93Gf2gyP+ccx7Vr9FtUMungdg@mail.gmail.com>

Hello Naresh and Everybody,

On 13/12/22 12:53, Naresh Kamboju wrote:
> On Mon, 12 Dec 2022 at 19:19, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>>
>> This is the start of the stable review cycle for the 4.19.269 release.
>> There are 49 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, 14 Dec 2022 13:08:57 +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.269-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.
>>
>> thanks,
>>
>> greg k-h
> 
> Results from Linaro’s test farm.
> No regressions on arm64, arm, x86_64, and i386.
> 
> Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> NOTE:
> arm clang-nightly allnoconfig builds failed due to these warnings / errors.
> for clang-nightly warning showing as error and for gcc-12 it is just a warning.
> 
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM=1 LLVM_IAS=0
> ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- HOSTCC=clang CC=clang
> arch/arm/mm/nommu.c:163:12: error: incompatible integer to pointer
> conversion assigning to 'void *' from 'phys_addr_t' (aka 'unsigned
> int') [-Wint-conversion]
>          zero_page = memblock_alloc(PAGE_SIZE, PAGE_SIZE);
>                    ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 1 error generated.
> make[2]: *** [/builds/linux/scripts/Makefile.build:303:
> arch/arm/mm/nommu.o] Error 1
> 
> commit causing this build failures,
>    ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation
>    [ Upstream commit 340a982825f76f1cff0daa605970fe47321b5ee7 ]

I've just submitted a patch to fix this:
https://patchwork.kernel.org/project/linux-arm-kernel/patch/20221213191813.4054267-1-giulio.benetti@benettiengineering.com/
and I've also submitted it to Russell King Patch system:
https://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=9280/1

Hope everything is correct.

Best regards
-- 
Giulio Benetti
CEO/CTO@Benetti Engineering sas

> 
> ## Build
> * kernel: 4.19.269-rc1
> * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
> * git branch: linux-4.19.y
> * git commit: bf741d1d7e6db2cb2fb6ba4634aaabad00089b40
> * git describe: v4.19.268-50-gbf741d1d7e6d
> * test details:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.19.y/build/v4.19.268-50-gbf741d1d7e6d
> 
> ## Test Regressions (compared to v4.19.268)
> 
> ## Metric Regressions (compared to v4.19.268)
> 
> ## Test Fixes (compared to v4.19.268)
> 
> ## Metric Fixes (compared to v4.19.268)
> 
> ## Test result summary
> total: 95070, pass: 81469, fail: 1691, skip: 10892, xfail: 1018
> 
> ## Build Summary
> * arc: 10 total, 10 passed, 0 failed
> * arm: 323 total, 316 passed, 7 failed
> * arm64: 59 total, 58 passed, 1 failed
> * i386: 29 total, 28 passed, 1 failed
> * mips: 46 total, 46 passed, 0 failed
> * parisc: 12 total, 12 passed, 0 failed
> * powerpc: 63 total, 63 passed, 0 failed
> * s390: 15 total, 15 passed, 0 failed
> * sh: 24 total, 24 passed, 0 failed
> * sparc: 12 total, 12 passed, 0 failed
> * x86_64: 53 total, 52 passed, 1 failed
> 
> ## Test suites summary
> * boot
> * fwts
> * igt-gpu-tools
> * kselftest-android
> * kselftest-arm64
> * kselftest-arm64/arm64.btitest.bti_c_func
> * kselftest-arm64/arm64.btitest.bti_j_func
> * kselftest-arm64/arm64.btitest.bti_jc_func
> * kselftest-arm64/arm64.btitest.bti_none_func
> * kselftest-arm64/arm64.btitest.nohint_func
> * kselftest-arm64/arm64.btitest.paciasp_func
> * kselftest-arm64/arm64.nobtitest.bti_c_func
> * kselftest-arm64/arm64.nobtitest.bti_j_func
> * kselftest-arm64/arm64.nobtitest.bti_jc_func
> * kselftest-arm64/arm64.nobtitest.bti_none_func
> * kselftest-arm64/arm64.nobtitest.nohint_func
> * kselftest-arm64/arm64.nobtitest.paciasp_func
> * kselftest-breakpoints
> * kselftest-capabilities
> * kselftest-cgroup
> * kselftest-clone3
> * kselftest-core
> * kselftest-cpu-hotplug
> * kselftest-cpufreq
> * kselftest-drivers-dma-buf
> * kselftest-efivarfs
> * kselftest-filesystems
> * kselftest-filesystems-binderfs
> * kselftest-firmware
> * kselftest-fpu
> * 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-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-vm
> * kselftest-x86
> * kselftest-zram
> * kunit
> * kvm-unit-tests
> * 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-open-posix-tests
> * ltp-pty
> * ltp-sched
> * ltp-securebits
> * ltp-smoke
> * ltp-syscalls
> * ltp-tracing
> * network-basic-tests
> * packetdrill
> * rcutorture
> * v4l2-compliance
> * vdso
> 
> --
> Linaro LKFT
> https://lkft.linaro.org


  reply	other threads:[~2022-12-13 19:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 13:18 [PATCH 4.19 00/49] 4.19.269-rc1 review Greg Kroah-Hartman
2022-12-12 18:14 ` Pavel Machek
2022-12-12 20:11 ` Jon Hunter
2022-12-12 20:22 ` Slade Watkins
2022-12-13  0:04 ` Shuah Khan
2022-12-13  0:24 ` Guenter Roeck
2022-12-13 11:53 ` Naresh Kamboju
2022-12-13 19:27   ` Giulio Benetti [this message]
2022-12-13 12:01 ` Sudip Mukherjee (Codethink)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0f674e79-5832-d296-4db2-ec9b0c40a298@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).