From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, stable@vger.kernel.org
Subject: Re: Please backport 2d43cc701b96 to v6.9 and v6.6
Date: Fri, 14 Jun 2024 10:45:47 +0200 [thread overview]
Message-ID: <2024061411-hypertext-saline-afb4@gregkh> (raw)
In-Reply-To: <87wmmsnelx.fsf@mail.lhotse>
On Fri, Jun 14, 2024 at 05:54:50PM +1000, Michael Ellerman wrote:
> Hi stable team,
>
> Can you please backport:
> 2d43cc701b96 ("powerpc/uaccess: Fix build errors seen with GCC 13/14")
>
> To v6.9 and v6.6.
>
> It was marked for backporting, but hasn't been picked up AFAICS. I'm not
> sure if it clashed with the asm_goto_output changes or something. But it
> backports cleanly to the current stable branches.
It's still in my "to get to queue" along with about 150+ other patches
that were tagged for stable inclusion. It's in good company, I'll get
to it after this current round of -rc releases is out.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: stable@vger.kernel.org, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Please backport 2d43cc701b96 to v6.9 and v6.6
Date: Fri, 14 Jun 2024 10:45:47 +0200 [thread overview]
Message-ID: <2024061411-hypertext-saline-afb4@gregkh> (raw)
In-Reply-To: <87wmmsnelx.fsf@mail.lhotse>
On Fri, Jun 14, 2024 at 05:54:50PM +1000, Michael Ellerman wrote:
> Hi stable team,
>
> Can you please backport:
> 2d43cc701b96 ("powerpc/uaccess: Fix build errors seen with GCC 13/14")
>
> To v6.9 and v6.6.
>
> It was marked for backporting, but hasn't been picked up AFAICS. I'm not
> sure if it clashed with the asm_goto_output changes or something. But it
> backports cleanly to the current stable branches.
It's still in my "to get to queue" along with about 150+ other patches
that were tagged for stable inclusion. It's in good company, I'll get
to it after this current round of -rc releases is out.
thanks,
greg k-h
next prev parent reply other threads:[~2024-06-14 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 7:54 Please backport 2d43cc701b96 to v6.9 and v6.6 Michael Ellerman
2024-06-14 8:45 ` Greg KH [this message]
2024-06-14 8:45 ` Greg KH
2024-06-14 11:32 ` Michael Ellerman
2024-06-14 11:32 ` Michael Ellerman
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=2024061411-hypertext-saline-afb4@gregkh \
--to=gregkh@linuxfoundation.org \
--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.