From: Michael Cree <mcree@orcon.net.nz>
To: Magnus Lindholm <linmag7@gmail.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
richard.henderson@linaro.org, mattst88@gmail.com,
macro@orcam.me.uk, macro@redhat.com, ink@unseen.parts,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
kees@kernel.org
Subject: Re: [PATCH 1/1] alpha: add support for SECCOMP and SECCOMP_FILTER
Date: Fri, 20 Feb 2026 11:51:20 +1300 [thread overview]
Message-ID: <aZeT6DcS8u1Qbq58@creeky> (raw)
In-Reply-To: <CA+=Fv5SPxzvJ3OCwfawOtUkBNmHJF=CS_9_m=a7QoHCn5UbUvA@mail.gmail.com>
On Thu, Feb 19, 2026 at 10:10:38PM +0100, Magnus Lindholm wrote:
> >
> > Thanks so much for working on this! Alpha and SPARC are the last two architectures
> > in Debian that are missing full support for SECCOMP filter. Great to see that Alpha
> > is now being worked on.
> >
> > FWIW, I haven't tested your patches yet, but I think you should also update the
> > documentation in Documentation/features/seccomp/seccomp-filter/arch-support.txt.
> >
>
> Thanks for taking a look! I'll put out a v2 of this patch, including
> an update to the
> documentation.
>
> > I will try to add support for Alpha in libseccomp over the weekend to test your patch.
> >
>
> Btw. I've tested your libseccomp with updated alpha support, real nice progress
Where is this updated libseccomp? I would like to test it too.
Cheers
Michael.
next prev parent reply other threads:[~2026-02-19 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 13:29 [PATCH 0/1] alpha: add support for SECCOMP and SECCOMP_FILTER Magnus Lindholm
2026-02-05 13:29 ` [PATCH 1/1] " Magnus Lindholm
2026-02-05 14:38 ` John Paul Adrian Glaubitz
2026-02-19 21:10 ` Magnus Lindholm
2026-02-19 22:51 ` Michael Cree [this message]
2026-02-19 23:06 ` 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=aZeT6DcS8u1Qbq58@creeky \
--to=mcree@orcon.net.nz \
--cc=glaubitz@physik.fu-berlin.de \
--cc=ink@unseen.parts \
--cc=kees@kernel.org \
--cc=linmag7@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=macro@redhat.com \
--cc=mattst88@gmail.com \
--cc=richard.henderson@linaro.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