From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755532AbcLOKsO (ORCPT ); Thu, 15 Dec 2016 05:48:14 -0500 Received: from mx2.suse.de ([195.135.220.15]:39626 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751214AbcLOKsM (ORCPT ); Thu, 15 Dec 2016 05:48:12 -0500 From: Petr Mladek To: Andrew Morton Cc: Linus Torvalds , Steven Rostedt , Peter Zijlstra , Sergey Senozhatsky , linux-kernel@vger.kernel.org, Petr Mladek Subject: [PATCH] MAINTAINERS: Add printk maintainers Date: Thu, 15 Dec 2016 11:47:58 +0100 Message-Id: <1481798878-31898-1-git-send-email-pmladek@suse.com> X-Mailer: git-send-email 1.8.5.6 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I and Sergey would like to volunteer as printk code maintainers. It is a code that everyone is using, various people fix bugs or even add features but there is nobody really interested into maintaining it. I and Sergey have put a lot of effort into understanding the code and related problems. We are working on solutions for some long term problems. There is a nice summary from the Kernel Summit presentation, see https://lwn.net/Articles/705938/ We have already started to use the gained knowledge and comment on other printk-related patches. The official role should help us to do it more effectively. Our priorities are: + prevent deadlocks (printk_safe patchset, console locks) + prevent softlocks (async printk, console_sem and flushing) + handle other bugs/fixes/features as they come with this in mind: + printk is used in different context + need special care in some modes, e.g. oops, panic, suspend + do best effort to store/show messages + the code is already pretty complicated and twisted; support clean ups; always think hard if a feature/fix is worth any complication Of course, it still will be much appreciated if other people review printk patches. Regarding the workflow. It will be highly appreciated if the patches might still go via Andrew's -mm tree at least for 4.10. In the long term, we would like to make Andrew's life easier and handle printk patches in an own git tree. But we first need to set it up and get familiar with the processes. Signed-off-by: Petr Mladek --- MAINTAINERS | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index c77e3bff262f..d8398bede04e 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -9728,6 +9728,13 @@ S: Supported F: Documentation/preempt-locking.txt F: include/linux/preempt.h +PRINTK +M: Petr Mladek +M: Sergey Senozhatsky +S: Maintained +F: kernel/printk/ +F: include/linux/printk.h + PRISM54 WIRELESS DRIVER M: "Luis R. Rodriguez" L: linux-wireless@vger.kernel.org -- 1.8.5.6