From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966464AbdLSE6x (ORCPT ); Mon, 18 Dec 2017 23:58:53 -0500 Received: from mail-pl0-f68.google.com ([209.85.160.68]:38728 "EHLO mail-pl0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S937528AbdLSE6u (ORCPT ); Mon, 18 Dec 2017 23:58:50 -0500 X-Google-Smtp-Source: ACJfBosTM6S8xOYoiGkT9wKrE3WNZDGN0gDriVmrWme4iJ3rkHW2cMtKOnq5jslnAbYOx0Dbq2QQtg== Date: Tue, 19 Dec 2017 13:58:46 +0900 From: Sergey Senozhatsky To: Steven Rostedt Cc: Sergey Senozhatsky , Petr Mladek , Tejun Heo , Sergey Senozhatsky , Jan Kara , Andrew Morton , Peter Zijlstra , Rafael Wysocki , Pavel Machek , Tetsuo Handa , linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCHv6 00/12] printk: introduce printing kernel thread Message-ID: <20171219045846.GE17164@jagdpanzerIV> References: <20171218133101.ri55uwivhc5xwg5y@pathway.suse.cz> <20171218133948.GD31274@jagdpanzerIV> <20171218141353.6shpvcwth34k6dsi@pathway.suse.cz> <20171218124613.1df152da@gandalf.local.home> <20171219010311.GB8892@jagdpanzerIV> <20171218200806.56a6507e@gandalf.local.home> <20171219012455.GB17164@jagdpanzerIV> <20171218210356.71a1f60e@vmware.local.home> <20171219024610.GC17164@jagdpanzerIV> <20171218223817.0e7f866e@vmware.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171218223817.0e7f866e@vmware.local.home> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (12/18/17 22:38), Steven Rostedt wrote: > On Tue, 19 Dec 2017 11:46:10 +0900 > Sergey Senozhatsky wrote: > > > anyway, > > before you guys push the patch to printk.git, can we wait for Tejun to > > run his tests against it? > > I've been asking for that since day one ;-) ok so you are not convinced that my scenarios real/matter; I'm not convinced that I have stable and functional boards with this patch ;) seems that we are coming to a dead end. for the record, I'm not going to block the patch if you want it to be merged. -ss