From: Michael Schmitz <schmitzmic@gmail.com>
To: linux-m68k@vger.kernel.org, geert@linux-m68k.org
Cc: glaubitz@physik.fu-berlin.de
Subject: [PATCH v12 0/3] Add kernel seccomp support for m68k
Date: Wed, 11 Jan 2023 09:22:40 +1300 [thread overview]
Message-ID: <20230110202243.29383-1-schmitzmic@gmail.com> (raw)
Merge conflict markers left over in v11 removed, version
number bumped in order to appease patch management tools.
No other changes from v11.
Cheers,
Michael
next reply other threads:[~2023-01-10 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 20:22 Michael Schmitz [this message]
2023-01-10 20:22 ` [PATCH v12 1/3] m68k/kernel - check syscall_trace_enter() return code on m68k Michael Schmitz
2023-01-10 20:22 ` [PATCH v12 2/3] m68k: add kernel seccomp support Michael Schmitz
2023-01-10 20:22 ` [PATCH v12 3/3] tools/testing - seccomp test fixes for m68k Michael Schmitz
2023-01-10 20:27 ` [PATCH v12 0/3] Add kernel seccomp support " John Paul Adrian Glaubitz
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=20230110202243.29383-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).