Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752187AbcCBNXA (ORCPT ); Wed, 2 Mar 2016 08:23:00 -0500 Received: from mail.skyhub.de ([78.46.96.112]:47517 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750992AbcCBNW6 (ORCPT ); Wed, 2 Mar 2016 08:22:58 -0500 Date: Wed, 2 Mar 2016 14:22:51 +0100 From: Borislav Petkov To: Michal Hocko Cc: Hidehiro Kawai , Andrew Morton , Thomas Mingarelli , Wim Van Sebroeck , Corey Minyard , Javi Merino , linux-watchdog@vger.kernel.org, "Steven Rostedt (Red Hat)" , Rasmus Villemoes , linux-kernel@vger.kernel.org, Michal Nazarewicz , Vitaly Kuznetsov , HATAYAMA Daisuke , Gobinda Charan Maji , Tejun Heo , Nicolas Iooss , openipmi-developer@lists.sourceforge.net, Borislav Petkov , Thomas Gleixner , Guenter Roeck Subject: Re: [v2 PATCH 1/3] panic: Change nmi_panic from macro to function Message-ID: <20160302132251.GH16954@pd.tnic> References: <20160302103624.5058.35844.stgit@softrs> <20160302103626.5058.74361.stgit@softrs> <20160302131824.GH26686@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20160302131824.GH26686@dhcp22.suse.cz> 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 Content-Length: 684 Lines: 22 On Wed, Mar 02, 2016 at 02:18:24PM +0100, Michal Hocko wrote: > On Wed 02-03-16 19:36:26, Hidehiro Kawai wrote: > [...] > > +void nmi_panic(struct pt_regs *regs, const char *fmt, ...) > > Do we really need vargs? All the current users seem to be OK with a > simple string. This makes the code slightly more complicated without any > apparent reason. I was just wondering the exactly same thing... The contra-arg would be that in case someone wants to do nmi_panic() with more than a string, then it won't work. The question is, does nmi_panic() even need to dump something more than regs and a string? -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.