From: Michael Schmitz <schmitzmic@gmail.com>
To: linux-m68k@vger.kernel.org, geert@linux-m68k.org
Cc: glaubitz@physik.fu-berlin.de
Subject: [PATCH v11 0/3] Add kernel seccomp support for m68k
Date: Tue, 10 Jan 2023 13:45:01 +1300 [thread overview]
Message-ID: <20230110004504.20292-1-schmitzmic@gmail.com> (raw)
Patch 1 from v10 of this series is now merged, so patch
numbering shifts by one.
Fixed a merge conflict in patch 2 (caused by change from
tracehook to ptrace API.
Added m68k seccomp self test support as patch 3.
Tested on ARAnyM, 63 out of 89 seccomp_bpf tests now pass
(33 with the old version).
Cheers,
Michael
next reply other threads:[~2023-01-10 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 0:45 Michael Schmitz [this message]
2023-01-10 0:45 ` [PATCH v11 1/3] m68k/kernel - check syscall_trace_enter() return code on m68k Michael Schmitz
2023-01-10 0:45 ` [PATCH v11 2/3] m68k: add kernel seccomp support Michael Schmitz
2023-01-10 17:00 ` Josh Juran
2023-01-10 19:12 ` Michael Schmitz
2023-01-10 0:45 ` [PATCH v11 3/3] tools/testing - seccomp test fixes for m68k 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=20230110004504.20292-1-schmitzmic@gmail.com \
--to=schmitzmic@gmail.com \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@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).