[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a9b38fe7-8a22-71b7-1e84-0ebf1e864306@kernel.org>
Date: Tue, 26 Jan 2021 11:30:02 -0600
From: Timur Tabi <timur@...nel.org>
To: Vlastimil Babka <vbabka@...e.cz>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Matthew Wilcox <willy@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
Petr Mladek <pmladek@...e.com>, roman.fietze@...na.com,
keescook@...omium.org, Steven Rostedt <rostedt@...dmis.org>,
John Ogness <john.ogness@...utronix.de>, linux-mm@...ck.org,
Akinobu Mita <akinobu.mita@...il.com>
Subject: Re: [PATCH 0/2] introduce DUMP_PREFIX_UNHASHED for hex dumps
On 1/26/21 11:14 AM, Vlastimil Babka wrote:
> If it was a boot option, I would personally be for leaving hashing enabled by
> default, with opt-in boot option to disable it.
A boot option would solve all my problems. I wouldn't need to recompile
the kernel, and it would apply to all variations of printk.
Powered by blists - more mailing lists