From: Finn Thain <fthain@linux-m68k.org>
To: Ulrich Hecht <uli@fpond.eu>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Michael Schmitz <schmitzmic@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH RFC v2 4/8] m68k: Handle arrivals of multiple signals correctly
Date: Tue, 13 Feb 2024 16:05:40 +1100 (AEDT) [thread overview]
Message-ID: <f3022b02-9859-1af1-1913-4215a12c1da8@linux-m68k.org> (raw)
In-Reply-To: <522961735.202648.1707732123771@webmail.strato.com>
[Cc: stable]
On Mon, 12 Feb 2024, Ulrich Hecht wrote:
>
> > On 02/08/2024 11:51 PM CET Finn Thain <fthain@linux-m68k.org> wrote:
> > Ulrich, I imagine that you would normally receive fixes via the
> > corresponding -stable trees. If Michael's series went into
> > stable/linux-4.19.y you could cherry-pick from there for your v4.4.y tree
> > and maybe avoid some merge conflicts that way.
>
> That would work for me.
>
OK. Here's the relevant commit. It fixes bd6f56a75bb2 which first appeared
in v2.6.38-rc1. I believe this can be cherry-picked without any conflicts.
50e43a573344 m68k: Update ->thread.esp0 before calling syscall_trace() in ret_from_signal
next prev parent reply other threads:[~2024-02-13 5:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 2:32 [PATCH RFC v2 0/8] m68k v4.4 backport fixes Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 1/8] m68k/mm: Adjust VM area to be unmapped by gap size for __iounmap() Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 2/8] m68k: Only force 030 bus error if PC not in exception table Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 3/8] m68k: include module.h to make use of exception handling in traps.c Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 4/8] m68k: Handle arrivals of multiple signals correctly Michael Schmitz
2024-02-05 8:10 ` Geert Uytterhoeven
2024-02-05 10:15 ` Michael Schmitz
2024-02-08 11:53 ` Ulrich Hecht
2024-02-08 22:51 ` Finn Thain
2024-02-12 0:48 ` Michael Schmitz
2024-02-12 10:02 ` Ulrich Hecht
2024-02-13 5:05 ` Finn Thain [this message]
2024-02-05 2:32 ` [PATCH RFC v2 5/8] m68k: Update ->thread.esp0 before calling syscall_trace() in ret_from_signal Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 6/8] m68k: Leave stack mangling to asm wrapper of sigreturn() Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 7/8] m68k: fix livelock in uaccess Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 8/8] m68k: Move signal frame following exception on 68020/030 Michael Schmitz
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=f3022b02-9859-1af1-1913-4215a12c1da8@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@gmail.com \
--cc=stable@vger.kernel.org \
--cc=uli@fpond.eu \
--cc=viro@zeniv.linux.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).