public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, 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,
	conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.1 000/791] 6.1.113-rc2 review
Date: Mon, 21 Oct 2024 11:45:10 +0200	[thread overview]
Message-ID: <2024102100-robust-shaking-8655@gregkh> (raw)
In-Reply-To: <f035e6ef-32e1-45a2-962e-dc27fa54271b@roeck-us.net>

On Sat, Oct 19, 2024 at 08:17:31AM -0700, Guenter Roeck wrote:
> On 10/15/24 04:26, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.113 release.
> > There are 791 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, 17 Oct 2024 11:22:41 +0000.
> > Anything received after that time might be too late.
> > 
> ...
> 
> > Nicholas Piggin <npiggin@gmail.com>
> >      powerpc/64: Option to build big-endian with ELFv2 ABI
> > 
> 
> With this patch in the tree, trying to build ppc:allmodconfig
> with gcc version 13.3 and binutils version 2.42 results in:
> 
> Error log:
> /tmp/cccUl45i.s: Assembler messages:
> /tmp/cccUl45i.s: Error: .size expression for gcm_init_p8 does not evaluate to a constant
> 
> and many other similar messages. The problem affects various drivers in
> drivers/crypto/vmx/. The problem afects all configurations with CRYPTO_DEV_VMX_ENCRYPT
> enabled.
> 
> Reverting the patch doesn't work because this patch is part of a larger series. However,
> I found that applying upstream commit 505ea33089dc ("powerpc/64: Add big-endian ELFv2
> flavour to crypto VMX asm generation") fixes the problem.

Now queued up, thanks.

greg k-h

      reply	other threads:[~2024-10-21  9:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 11:26 [PATCH 6.1 000/791] 6.1.113-rc2 review Greg Kroah-Hartman
2024-10-15 15:34 ` Ron Economos
2024-10-15 17:33 ` Florian Fainelli
2024-10-16  8:15 ` Naresh Kamboju
2024-10-16  8:50 ` Naresh Kamboju
2024-10-16  9:21 ` Pavel Machek
2024-10-16 10:01 ` Jon Hunter
2024-10-16 12:51 ` Miguel Ojeda
2024-10-17 12:30 ` Muhammad Usama Anjum
2024-10-19 15:17 ` Guenter Roeck
2024-10-21  9:45   ` Greg Kroah-Hartman [this message]

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=2024102100-robust-shaking-8655@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.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=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