public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Kees Cook <keescook@chromium.org>,
	Linux API <linux-api@vger.kernel.org>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [PATCH 08/17] ptrace/m68k: Stop open coding ptrace_report_syscall
Date: Wed, 12 Jan 2022 14:32:51 +1100 (AEDT)	[thread overview]
Message-ID: <b8ad3fc-523f-eca2-91d7-c77d20a1e876@linux-m68k.org> (raw)
In-Reply-To: <6060f799-d0c5-e4c2-a81c-2bd872ce3d5a@gmail.com>

On Wed, 12 Jan 2022, Michael Schmitz wrote:

> 
> I seem to recall we also tested those on your 040 and there was no 
> regression there, but I may be misremembering that.
> 

I abandoned that regression testing exercise when unpatched mainline 
kernels began failing on that machine. I'm in the process of setting up a 
different 68040 machine.

  reply	other threads:[~2022-01-12  3:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r19opkx1.fsf_-_@email.froward.int.ebiederm.org>
     [not found] ` <20220103213312.9144-8-ebiederm@xmission.com>
     [not found]   ` <CAMuHMdWsNBjOJh0QEx9sppA9x3WoL8H2icqukNqECFhOPremjw@mail.gmail.com>
     [not found]     ` <YdxcszwEslyQJSuF@zeniv-ca.linux.org.uk>
2022-01-10 17:54       ` [PATCH 08/17] ptrace/m68k: Stop open coding ptrace_report_syscall Geert Uytterhoeven
2022-01-10 20:37         ` Al Viro
2022-01-10 21:18           ` Eric W. Biederman
2022-01-11  1:33         ` Michael Schmitz
2022-01-11 22:42           ` Finn Thain
2022-01-12  0:20             ` Michael Schmitz
2022-01-12  3:32               ` Finn Thain [this message]
2022-01-12  7:54                 ` Michael Schmitz
2022-01-12  7:55               ` Geert Uytterhoeven
2022-01-12  8:05                 ` 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=b8ad3fc-523f-eca2-91d7-c77d20a1e876@linux-m68k.org \
    --to=fthain@linux-m68k.org \
    --cc=ebiederm@xmission.com \
    --cc=geert@linux-m68k.org \
    --cc=keescook@chromium.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=oleg@redhat.com \
    --cc=schmitzmic@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --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