From: Greg KH <greg@kroah.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, stable@vger.kernel.org
Subject: Re: [PATCH v5.10] powerpc/uaccess: Fix build errors seen with GCC 13/14
Date: Mon, 17 Jun 2024 14:28:14 +0200 [thread overview]
Message-ID: <2024061706-dingy-constant-fd27@gregkh> (raw)
In-Reply-To: <20240614112714.3482739-1-mpe@ellerman.id.au>
On Fri, Jun 14, 2024 at 09:27:14PM +1000, Michael Ellerman wrote:
> commit 2d43cc701b96f910f50915ac4c2a0cae5deb734c upstream.
>
> Building ppc64le_defconfig with GCC 14 fails with assembler errors:
>
All backports now queued up,t hanks!
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: stable@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v5.10] powerpc/uaccess: Fix build errors seen with GCC 13/14
Date: Mon, 17 Jun 2024 14:28:14 +0200 [thread overview]
Message-ID: <2024061706-dingy-constant-fd27@gregkh> (raw)
In-Reply-To: <20240614112714.3482739-1-mpe@ellerman.id.au>
On Fri, Jun 14, 2024 at 09:27:14PM +1000, Michael Ellerman wrote:
> commit 2d43cc701b96f910f50915ac4c2a0cae5deb734c upstream.
>
> Building ppc64le_defconfig with GCC 14 fails with assembler errors:
>
All backports now queued up,t hanks!
greg k-h
next prev parent reply other threads:[~2024-06-17 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 11:27 [PATCH v5.10] powerpc/uaccess: Fix build errors seen with GCC 13/14 Michael Ellerman
2024-06-14 11:27 ` Michael Ellerman
2024-06-17 12:28 ` Greg KH [this message]
2024-06-17 12:28 ` Greg KH
2024-06-17 16:21 ` Segher Boessenkool
2024-06-17 16:21 ` Segher Boessenkool
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=2024061706-dingy-constant-fd27@gregkh \
--to=greg@kroah.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.