From: Jonathan Corbet <corbet@lwn.net>
To: Beau Belgrave <beaub@linux.microsoft.com>,
rostedt@goodmis.org, mhiramat@kernel.org
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: Document user_events ioctl code
Date: Tue, 16 Jul 2024 11:15:43 -0600 [thread overview]
Message-ID: <87msmhtg00.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240715181413.1157-1-beaub@linux.microsoft.com>
Beau Belgrave <beaub@linux.microsoft.com> writes:
> The user events trace subsystem uses the 0x2A/'*' code for ioctls. These
> are published via the uapi/linux/user_events.h header file.
>
> Add a line indicating user events as the owner of the 0x2A/'*' code and
> reserve the first 32 sequence numbers.
>
> Signed-off-by: Beau Belgrave <beaub@linux.microsoft.com>
> ---
> V2 Changes: Reserved first 32 sequence numbers for growth.
>
> Documentation/userspace-api/ioctl/ioctl-number.rst | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/userspace-api/ioctl/ioctl-number.rst b/Documentation/userspace-api/ioctl/ioctl-number.rst
> index a141e8e65c5d..d953549f0b2b 100644
> --- a/Documentation/userspace-api/ioctl/ioctl-number.rst
> +++ b/Documentation/userspace-api/ioctl/ioctl-number.rst
> @@ -97,6 +97,8 @@ Code Seq# Include File Comments
> '%' 00-0F include/uapi/linux/stm.h System Trace Module subsystem
> <mailto:alexander.shishkin@linux.intel.com>
> '&' 00-07 drivers/firewire/nosy-user.h
> +'*' 00-1F uapi/linux/user_events.h User Events Subsystem
> + <mailto:linux-trace-kernel@vger.kernel.org>
I've applied this, thanks.
jon
prev parent reply other threads:[~2024-07-16 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 18:14 Beau Belgrave
2024-07-16 17:15 ` Jonathan Corbet [this message]
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=87msmhtg00.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=beaub@linux.microsoft.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®