[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161019134233.GB594@swordfish>
Date: Wed, 19 Oct 2016 22:42:33 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc: Petr Mladek <pmladek@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jan Kara <jack@...e.cz>, Tejun Heo <tj@...nel.org>,
Calvin Owens <calvinowens@...com>,
Thomas Gleixner <tglx@...utronix.de>,
Mel Gorman <mgorman@...hsingularity.net>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Subject: Re: [RFC][PATCHv3 3/6] printk: introduce per-cpu safe_print seq
buffer
On (10/19/16 00:40), Sergey Senozhatsky wrote:
> -obj-y = printk.o
> -obj-$(CONFIG_PRINTK_NMI) += printk_safe.o
> +obj-y = printk_safe.o printk.o
[..]
d'oh... this breaks !PRINTK configs. will fix in v4.
-ss
Powered by blists - more mailing lists