From: "Dmitry V. Levin" <ldv@strace.io>
To: Alejandro Colomar <alx@kernel.org>
Cc: Marco Cavenati <Marco.Cavenati@eurecom.fr>, linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man2/ptrace.2: Add PTRACE_SET_SYSCALL_INFO, update struct ptrace_syscall_info
Date: Tue, 10 Feb 2026 22:53:47 +0200 [thread overview]
Message-ID: <20260210205347.GA31604@strace.io> (raw)
In-Reply-To: <aYuRZuZIQCMw1gqP@devuan>
Hi,
On Tue, Feb 10, 2026 at 09:14:29PM +0100, Alejandro Colomar wrote:
> Hi Marco, Dmitry,
>
> I'm back. :-)
>
> On 2026-01-21T18:56:39+0200, Dmitry V. Levin wrote:
> > On Wed, Jan 21, 2026 at 04:55:41PM +0100, Marco Cavenati wrote:
> > > Add documentation for the new ptrace request PTRACE_SET_SYSCALL_INFO,
> > > introduced in Linux 6.16.
> > >
> > > Add 'reserved' and 'flags' fields of struct ptrace_syscall_info.
> > >
> > > This description is based on kernel commit 26bb32768fe6552de044f782a58b3272073fbfc0
> > > ("ptrace: introduce PTRACE_SET_SYSCALL_INFO request") by Dmitry V. Levin.
> > >
> > > Signed-off-by: Marco Cavenati <Marco.Cavenati@eurecom.fr>
>
> Thanks! I've applied the patch.
>
> > > ---
> > > AUTHORS | 1 +
> > > man/man2/ptrace.2 | 21 +++++++++++++++++++++
> > > 2 files changed, 22 insertions(+)
> > >
> > > diff --git a/AUTHORS b/AUTHORS
> > > index 9035d405a..f332932e1 100644
> > > --- a/AUTHORS
> > > +++ b/AUTHORS
> [...]
>
> > Looks good, thanks!
>
> Should I take that as a Reviewed-by?
Feel free to add:
Reviewed-by: Dmitry V. Levin <ldv@strace.io>
--
ldv
next prev parent reply other threads:[~2026-02-10 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 15:55 [PATCH] man/man2/ptrace.2: Add PTRACE_SET_SYSCALL_INFO, update struct ptrace_syscall_info Marco Cavenati
2026-01-21 16:56 ` Dmitry V. Levin
2026-02-10 20:14 ` Alejandro Colomar
2026-02-10 20:53 ` Dmitry V. Levin [this message]
2026-02-10 21:20 ` Alejandro Colomar
2026-02-10 21:41 ` Dmitry V. Levin
2026-02-10 21:52 ` Alejandro Colomar
2026-02-07 11:59 ` Marco Cavenati
2026-02-07 18:24 ` Alejandro Colomar
2026-02-07 18:38 ` Marco Cavenati
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=20260210205347.GA31604@strace.io \
--to=ldv@strace.io \
--cc=Marco.Cavenati@eurecom.fr \
--cc=alx@kernel.org \
--cc=linux-man@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.