public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-kernel@vger.kernel.org, stable@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, slade@sladewatkins.com
Subject: Re: [PATCH 5.15 000/229] 5.15.54-rc2 review
Date: Tue, 12 Jul 2022 09:12:59 +0200	[thread overview]
Message-ID: <Ys0e+4B+IFUDroFX@kroah.com> (raw)
In-Reply-To: <CA+G9fYsvtJu832j-1NmJ00ZOvGLAxAHUkNWo8PDztT--oO0_Ng@mail.gmail.com>

On Tue, Jul 12, 2022 at 09:14:21AM +0530, Naresh Kamboju wrote:
> On Mon, 11 Jul 2022 at 20:24, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.15.54 release.
> > There are 229 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, 13 Jul 2022 14:51:35 +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/v5.x/stable-review/patch-5.15.54-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-5.15.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> 
> Results from Linaro’s test farm.
> Regressions found while building for powerpc.
> 
> Following powerpc builds failed.
> 
> * powerpc, build
>   - clang-13-defconfig
>   - clang-13-ppc64e_defconfig
>   - clang-14-defconfig
>   - clang-14-ppc64e_defconfig
>   - gcc-10-cell_defconfig
>   - gcc-10-defconfig
>   - gcc-10-maple_defconfig
>   - gcc-10-ppc64e_defconfig
>   - gcc-11-cell_defconfig
>   - gcc-11-defconfig
>   - gcc-11-maple_defconfig
>   - gcc-11-ppc64e_defconfig
>   - gcc-8-cell_defconfig
>   - gcc-8-defconfig
>   - gcc-8-maple_defconfig
>   - gcc-8-ppc64e_defconfig
>   - gcc-9-cell_defconfig
>   - gcc-9-defconfig
>   - gcc-9-maple_defconfig
>   - gcc-9-ppc64e_defconfig
>   - gcc-11-allmodconfig
>   - gcc-10-allmodconfig
>   - clang-13-allmodconfig
>   - clang-14-allmodconfig
> 
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM=1 LLVM_IAS=0
> LD=powerpc64le-linux-gnu-ld ARCH=powerpc
> CROSS_COMPILE=powerpc64le-linux-gnu- 'HOSTCC=sccache clang'
> 'CC=sccache clang'
> arch/powerpc/kernel/vdso64/gettimeofday.S: Assembler messages:
> arch/powerpc/kernel/vdso64/gettimeofday.S:25: Error: unrecognized
> opcode: `cvdso_call'
> arch/powerpc/kernel/vdso64/gettimeofday.S:36: Error: unrecognized
> opcode: `cvdso_call'
> arch/powerpc/kernel/vdso64/gettimeofday.S:47: Error: unrecognized
> opcode: `cvdso_call'
> arch/powerpc/kernel/vdso64/gettimeofday.S:57: Error: unrecognized
> opcode: `cvdso_call_time'
> clang: error: assembler command failed with exit code 1 (use -v to see
> invocation)
> make[2]: *** [scripts/Makefile.build:390:
> arch/powerpc/kernel/vdso64/gettimeofday.o] Error 1
> make[2]: Target 'include/generated/vdso64-offsets.h' not remade
> because of errors.
> make[1]: *** [arch/powerpc/Makefile:427: vdso_prepare] Error 2
> 
> Build : https://builds.tuxbuild.com/2BnsQzulG0EbhdbiIORptHZwacG/
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

Thanks, let me push out a -rc3 with the powerpc vdso patches removed.

greg k-h

  reply	other threads:[~2022-07-12  7:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 14:54 [PATCH 5.15 000/229] 5.15.54-rc2 review Greg Kroah-Hartman
2022-07-11 18:37 ` Florian Fainelli
2022-07-12  1:19 ` Guenter Roeck
2022-07-12  7:12   ` Greg Kroah-Hartman
2022-07-12  2:35 ` Shuah Khan
2022-07-12  3:44 ` Naresh Kamboju
2022-07-12  7:12   ` Greg Kroah-Hartman [this message]
2022-07-12  7:48 ` Ron Economos
2022-07-12  8:13 ` Bagas Sanjaya
2022-07-12  9:18 ` Jon Hunter

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=Ys0e+4B+IFUDroFX@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --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=pavel@denx.de \
    --cc=shuah@kernel.org \
    --cc=slade@sladewatkins.com \
    --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