From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S942366AbcJSO32 (ORCPT ); Wed, 19 Oct 2016 10:29:28 -0400 Received: from mail-pf0-f169.google.com ([209.85.192.169]:36451 "EHLO mail-pf0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S942295AbcJSO3M (ORCPT ); Wed, 19 Oct 2016 10:29:12 -0400 Date: Wed, 19 Oct 2016 20:48:28 +0900 From: Sergey Senozhatsky To: Peter Zijlstra Cc: Sergey Senozhatsky , Petr Mladek , Andrew Morton , Jan Kara , Tejun Heo , Calvin Owens , Thomas Gleixner , Mel Gorman , Steven Rostedt , Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] make printk work again Message-ID: <20161019114828.GA414@swordfish> References: <20161018170830.405990950@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161018170830.405990950@infradead.org> User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (10/18/16 19:08), Peter Zijlstra wrote: > This basically fixes printk by evading everything it does. > > There's too many problems with printk, from sleeping locks to broken console > drivers. Stop using it. > > The early_console drivers are the most robust and simple, use those. ACK Can we also please ban that pre Because it's a bit tricky.emption thing? -ss