From: Ivan Kokshaysky <ink@unseen.parts>
To: gregkh@linuxfoundation.org
Cc: linmag7@gmail.com, macro@orcam.me.uk, mattst88@gmail.com,
stable@vger.kernel.org
Subject: Re: Patch "alpha: make stack 16-byte aligned (most cases)" has been added to the 6.6-stable tree
Date: Tue, 18 Feb 2025 14:40:38 +0100 [thread overview]
Message-ID: <Z7SN1kaT-1tuYyvL@minute> (raw)
In-Reply-To: <2025021844-cruelness-freedom-e051@gregkh>
On Tue, Feb 18, 2025 at 01:55:45PM +0100, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> alpha: make stack 16-byte aligned (most cases)
Hi Greg, thanks for applying this!
> Patches currently in stable-queue which might be from ink@unseen.parts are
>
> queue-6.6/alpha-make-stack-16-byte-aligned-most-cases.patch
> queue-6.6/alpha-align-stack-for-page-fault-and-user-unaligned-trap-handlers.patch
The third one (commit 77b823fa619f97d alpha: replace hardcoded stack offsets
with autogenerated ones) is also needed, but it won't apply as-is to 6.6
and older kernels.
Do you want me to provide the patches?
Ivan.
next parent reply other threads:[~2025-02-18 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025021844-cruelness-freedom-e051@gregkh>
2025-02-18 13:40 ` Ivan Kokshaysky [this message]
2025-02-18 14:04 ` Patch "alpha: make stack 16-byte aligned (most cases)" has been added to the 6.6-stable tree Greg KH
2025-02-18 14:50 ` [PATCH][v4.19-v6.1] alpha: replace hardcoded stack offsets with autogenerated Ivan Kokshaysky
2025-02-18 14:52 ` [PATCH][v6.6.x] alpha: replace hardcoded stack offsets with autogenerated ones Ivan Kokshaysky
2025-02-18 15:12 ` Greg KH
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=Z7SN1kaT-1tuYyvL@minute \
--to=ink@unseen.parts \
--cc=gregkh@linuxfoundation.org \
--cc=linmag7@gmail.com \
--cc=macro@orcam.me.uk \
--cc=mattst88@gmail.com \
--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 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).