linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	 Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Beau Belgrave <beaub@linux.microsoft.com>
Subject: Re: [GIT PULL] tracing/tracefs: Fixes for v6.9
Date: Fri, 3 May 2024 17:01:08 -0700	[thread overview]
Message-ID: <CAHk-=wgMSaivGRNk55fd8F3yODqOYUtY=d+vnXmY2buUKewd8Q@mail.gmail.com> (raw)
In-Reply-To: <20240503190728.7510af9a@gandalf.local.home>

On Fri, 3 May 2024 at 16:07, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> - Minor fix for user_events interface
>   The ABI of creating a user event states that the fields
>   are separated by semicolons, and spaces should be ignored.
>   But the parsing expected at least one space to be there (which was incorrect).
>   Fix the reading of the string to handle fields separated by
>   semicolons but no space between them.

This is the opposite of a fix.

A fix would have fixed the documentation to match reality.

Instead, this relaxes our existing parsing. Are there any old kernels
that had that relaxed parsing? Is there any actual reason to not just
fix documentation to match reality?

Because when reality and documentation do not match, it is not
*REALITY* that is buggy.

               Linus

  reply	other threads:[~2024-05-04  0:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 23:07 [GIT PULL] tracing/tracefs: Fixes for v6.9 Steven Rostedt
2024-05-04  0:01 ` Linus Torvalds [this message]
2024-05-04  1:22   ` Steven Rostedt

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='CAHk-=wgMSaivGRNk55fd8F3yODqOYUtY=d+vnXmY2buUKewd8Q@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=beaub@linux.microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --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;
as well as URLs for NNTP newsgroup(s).