From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 53431908 for ; Mon, 31 Oct 2016 18:26:56 +0000 (UTC) Received: from smtp.nue.novell.com (smtp.nue.novell.com [195.135.221.5]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 80BFB19E for ; Mon, 31 Oct 2016 18:26:55 +0000 (UTC) To: ksummit-discuss@lists.linuxfoundation.org References: <20160719034717.GA24189@swordfish> <20160921044156.GA486@swordfish> <20161031065435.GA458@swordfish> <20161031135617.bs7df7kur23gvm6b@thunk.org> <20161031145655.GA433@swordfish> <20161031161824.3knff5u3m6mipelv@thunk.org> <20161031182133.GA490@swordfish> From: Hannes Reinecke Message-ID: <942546fc-0de1-a253-05f3-e9e39020e0c9@suse.com> Date: Mon, 31 Oct 2016 19:26:45 +0100 MIME-Version: 1.0 In-Reply-To: <20161031182133.GA490@swordfish> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Ksummit-discuss] [TECH TOPIC] printk considered harmful List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 10/31/2016 07:21 PM, Sergey Senozhatsky wrote: > Hello, > > On (10/31/16 12:18), Theodore Ts'o wrote: >> On Mon, Oct 31, 2016 at 11:56:55PM +0900, Sergey Senozhatsky wrote: >>> ok, thanks. I personally will have some conflicts on Wed - "Open >>> panel for discussing MM problems" and some of LPC microconfs. >> >> would 10:00am (after the MM panel) work for you and others? > > speaking for myself only, > if there are no better options, then I'm OK with Wed 10am. I'd like > to be in Sweeney AB starting from 11:20am, but can sacrifice it, if > need be (in case if 10am doesn't work for someone. or if 1hr won't > be enough (which is quite likely)). so let's hear from others. > >>> and I'd love to change the topic name since async printk is just >>> 25% of the issue we want to discuss. the list I'm looking at now >>> is as follows: >>> >>> 1) deadlocks in printk and printk recursion >>> 2) async printk >>> 3) pr_cont >>> 4) console semaphore scalability and problems >> >> So a topic name like "printk improvements" would be better? > > "printk considered harmful" sounds good as well :) but "printk improvements" > can surely work. > I'd like to join, too. Personally I would prefer Tue, but the proposed time on Wed would work for me, too. Cheers, Hannes