From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759011AbcKDEqz (ORCPT ); Fri, 4 Nov 2016 00:46:55 -0400 Received: from mx2.suse.de ([195.135.220.15]:47103 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756247AbcKDEqw (ORCPT ); Fri, 4 Nov 2016 00:46:52 -0400 Date: Fri, 4 Nov 2016 00:28:27 +0100 From: Jan Kara To: Sergey Senozhatsky Cc: Joe Perches , Jiri Kosina , Theodore Tso , Hannes Reinecke , Jan Kara , Petr Mladek , linux-kernel@vger.kernel.org Subject: Re: printk considered harmful (was: [TECH TOPIC] asynchronous printk) Message-ID: <20161103232827.GE24234@quack2.suse.cz> References: <1478106396.23018.51.camel@perches.com> <20161103173153.GA423@swordfish> <20161103180131.GC423@swordfish> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161103180131.GC423@swordfish> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 04-11-16 03:01:31, Sergey Senozhatsky wrote: > fix a typo > > On (11/04/16 02:31), Sergey Senozhatsky wrote: > [..] > > #4 console semaphore > > discussion outcome: > > we agreed that we can do better here and that it makes sense to do > ^^^^ IOW, console semaphore thing > can be improved > > > what's been proposed in my slides. but, I keep it as a low priority. > > frankly. I'd be happy to see #1-#3 in the mainline in 9-12 months. > ^^^^ #1-#2, of course. but #1 consists > of 2 steps. > > I'm still not entirely sure if I want to split async pintk and printk > deadlock rework. these things want to come together, for a number of > reasons. or, at least, push the async printk before printk deadlock > rework. Yep, please push async printk patches soon. IMHO there's no reason to wait with that. You can create a git tree with printk patches and push it directly to Linus since he seems to be fine with the approach... Honza -- Jan Kara SUSE Labs, CR