[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wg24KPFfeNwYdsD0e79MP4QhO3VaWkh0buPSD0M=141xQ@mail.gmail.com>
Date: Sat, 16 Mar 2024 09:31:10 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Beau Belgrave <beaub@...ux.microsoft.com>,
Chengming Zhou <zhouchengming@...edance.com>, Huang Yiwei <quic_hyiwei@...cinc.com>,
John Garry <john.g.garry@...cle.com>, Randy Dunlap <rdunlap@...radead.org>,
Thorsten Blum <thorsten.blum@...lux.com>, Vincent Donnefort <vdonnefort@...gle.com>,
linke li <lilinke99@...com>, Daniel Bristot de Oliveira <bristot@...hat.com>
Subject: Re: [GIT PULL] tracing: Updates for v6.9
On Fri, 15 Mar 2024 at 09:27, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> - Add ring_buffer memory mappings
I pulled this, looked at it, and unpulled it again.
I don't want to have years of "fix up the mistakes after the fact".
This is all done entirely incorrectly, and just as an example of that,
subbuf_map_prepare() is another case of "tracing code works around the
fact that it did things wrong in the first place".
So instead of merging a new feature that was mis-designed and is
already having code working around its mis-design, I'm not merging it
at all.
Linus
Powered by blists - more mailing lists