[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023091552-sanitizer-vertigo-8a75@gregkh>
Date: Fri, 15 Sep 2023 11:51:54 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Enlin Mu <enlin.mu@...look.com>
Cc: pmladek@...e.com, rostedt@...dmis.org, john.ogness@...utronix.de,
senozhatsky@...omium.org, keescook@...omium.org,
tony.luck@...el.com, gpiccoli@...lia.com, enlin.mu@...soc.com,
enlinmu@...il.com, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH] printk: add cpu id information to printk() output
On Fri, Sep 15, 2023 at 03:40:34PM +0800, Enlin Mu wrote:
> From: Enlin Mu <enlin.mu@...soc.com>
>
> Sometimes we want to print cpu id of printk() messages to consoles
This is rejected every few years. What has changes from the previous
times this was sent?
And why can't you use trace_printk()?
thanks,
greg k-h
Powered by blists - more mailing lists