public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Ulrich Hecht <uli@fpond.eu>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: cip-dev@lists.cip-project.org, linux-m68k@vger.kernel.org,
	geert@linux-m68k.org, fthain@linux-m68k.org,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH v4 0/2] m68k v4.4 backport fixes (resend)
Date: Mon, 30 Sep 2024 10:05:28 +0200 (CEST)	[thread overview]
Message-ID: <282827158.1735339.1727683528989@webmail.strato.de> (raw)
In-Reply-To: <20240930020840.15226-1-schmitzmic@gmail.com>

> On 09/30/2024 4:08 AM CEST Michael Schmitz <schmitzmic@gmail.com> wrote:
> Resend (partial) of my CIP v4.4 backport patches for m68k.
> 
> This series only contains patches 4 and 5 of the previous
> series (Al Viro's signal handling fixes) - everything else
> appears to have been applied in the meantime, or isn't
> really a bugfix. These patches need merge conflict fixes
> and are not suitable for cherry-picking from v4.19.y.

Thanks, applied.

> Tested on 60830 (Atari Falcon)

Are you using atari_defconfig? If not, could you send me the kernel config for reference?

CU
Uli


  parent reply	other threads:[~2024-09-30  8:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30  2:08 [PATCH v4 0/2] m68k v4.4 backport fixes (resend) Michael Schmitz
2024-09-30  2:08 ` [PATCH v4 1/2] m68k: Handle arrivals of multiple signals correctly Michael Schmitz
2024-09-30  2:08 ` [PATCH v4 2/2] m68k: Update ->thread.esp0 before calling syscall_trace() in ret_from_signal Michael Schmitz
2024-09-30  8:05 ` Ulrich Hecht [this message]
2024-10-01  1:49   ` [PATCH v4 0/2] m68k v4.4 backport fixes (resend) 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=282827158.1735339.1727683528989@webmail.strato.de \
    --to=uli@fpond.eu \
    --cc=cip-dev@lists.cip-project.org \
    --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