From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933659AbcLABHB (ORCPT ); Wed, 30 Nov 2016 20:07:01 -0500 Received: from mail-pg0-f66.google.com ([74.125.83.66]:34573 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751758AbcLABG5 (ORCPT ); Wed, 30 Nov 2016 20:06:57 -0500 Date: Thu, 1 Dec 2016 10:07:01 +0900 From: Sergey Senozhatsky To: Petr Mladek Cc: Sergey Senozhatsky , Andrew Morton , Jan Kara , Tejun Heo , Calvin Owens , Thomas Gleixner , Mel Gorman , Steven Rostedt , Ingo Molnar , Peter Zijlstra , Laura Abbott , Andy Lutomirski , Linus Torvalds , Kees Cook , linux-kernel@vger.kernel.org, Sergey Senozhatsky Subject: Re: [RFC][PATCHv4 2/6] printk: rename nmi.c and exported api Message-ID: <20161201010701.GC12039@jagdpanzerIV> References: <20161027154933.1211-1-sergey.senozhatsky@gmail.com> <20161027154933.1211-3-sergey.senozhatsky@gmail.com> <20161124163501.GF24103@pathway.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161124163501.GF24103@pathway.suse.cz> 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 (11/24/16 17:35), Petr Mladek wrote: [..] > > #ifdef CONFIG_PRINTK_NMI > > -extern void printk_nmi_init(void); > > -extern void printk_nmi_enter(void); > > -extern void printk_nmi_exit(void); > > -extern void printk_nmi_flush(void); > > -extern void printk_nmi_flush_on_panic(void); > > +extern void printk_safe_init(void); > > +extern void printk_safe_nmi_enter(void); > > +extern void printk_safe_nmi_exit(void); > > I would personally keep the short names pritnk_nmi_enter() and > printk_nmi_exit(). These are the only functions that will stay > in this CONFIG_PRINT_NMI section. The others are generic and > will be moved to the generic section in the next patch. I'd probably prefer all printk_safe functions to be printk_safe prefixed, just to show the fact that those are printk_safe functions (IOW, indirect output to a per-CPU buffer and flush it to logbuf later). > Well, it is just a cosmetic problem and a personal opinion. > The patch makes sense and looks fine: > > Reviewed-by: Petr Mladek thanks. -ss