From: Ulrich Hecht <uli@fpond.eu>
To: Michael Schmitz <schmitzmic@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, fthain@linux-m68k.org,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH RFC v2 4/8] m68k: Handle arrivals of multiple signals correctly
Date: Thu, 8 Feb 2024 12:53:58 +0100 (CET) [thread overview]
Message-ID: <1501038841.1120470.1707393238298@webmail.strato.com> (raw)
In-Reply-To: <401b6911-e6ed-3e9f-9dcc-d4f951c6beef@gmail.com>
> On 02/05/2024 11:15 AM CET Michael Schmitz <schmitzmic@gmail.com> wrote:
> On that note - Uli: would you prefer the entire backport series, or only
> those you do not already have?
I'd prefer to only get what's missing.
CU
Uli
next prev parent reply other threads:[~2024-02-08 12:12 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 [this message]
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
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=1501038841.1120470.1707393238298@webmail.strato.com \
--to=uli@fpond.eu \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@gmail.com \
--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