[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <62546379-a2b8-bbbb-0799-3afd9b15960a@i-love.sakura.ne.jp>
Date: Tue, 6 Apr 2021 14:31:43 +0900
From: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To: Jiri Slaby <jirislaby@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
John Ogness <john.ogness@...utronix.de>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tty: use printk_safe context at tty_msg()
On 2021/04/06 13:51, Jiri Slaby wrote:
> On 03. 04. 21, 6:14, Tetsuo Handa wrote:
>> --- a/include/linux/tty.h
>> +++ b/include/linux/tty.h
>> @@ -14,6 +14,7 @@
>> #include <uapi/linux/tty.h>
>> #include <linux/rwsem.h>
>> #include <linux/llist.h>
>> +#include <../../kernel/printk/internal.h>
>
> Including printk's internal header in linux/tty.h doesn't look correct to me.
>
This is because this patch wants __printk_safe_enter()/__printk_safe_exit()
without #ifdef'ing CONFIG_PRINTK.
Peter and Sergey, what should we do?
Can we move printk_safe_enter_irqsave()/printk_safe_exit_irqrestore() to include/linux/printk.h ?
Powered by blists - more mailing lists