.com, [email protected], [email protected], [email protected], 
[email protected], [email protected], [email protected], 
[email protected], [email protected], [email protected], 
[email protected], [email protected], [email protected], 
[email protected], [email protected], Peter Zijlstra <[email protected]>, 
[email protected], [email protected], [email protected], 
[email protected], [email protected], 
[email protected], [email protected], 
[email protected], Arnd Bergmann <[email protected]>, [email protected], 
[email protected], [email protected], [email protected], 
[email protected], [email protected], [email protected], 
[email protected], [email protected], 
[email protected], [email protected], [email protected], 
[email protected], [email protected], [email protected], 
[email protected], [email protected], palmer
 @dabbelt.com, [email protected], [email protected], 
[email protected], [email protected]
Errors-To: [email protected]
Sender: "Linuxppc-dev" 
<[email protected]>

On Thu, 9 Jun 2022 15:02:20 +0200
Petr Mladek <[email protected]> wrote:

> > I'm somewhat curious whether we can actually remove that trace event.  
> 
> Good question.
> 
> Well, I think that it might be useful. It allows to see trace and
> printk messages together.

Yes people still use it. I was just asked about it at Kernel Recipes. That
is, someone wanted printk mixed in with the tracing, and I told them about
this event (which they didn't know about but was happy to hear that it
existed).

-- Steve

Reply via email to