Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754295AbZKPVf0 (ORCPT ); Mon, 16 Nov 2009 16:35:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753951AbZKPVf0 (ORCPT ); Mon, 16 Nov 2009 16:35:26 -0500 Received: from relay3.sgi.com ([192.48.152.1]:39694 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753924AbZKPVfZ (ORCPT ); Mon, 16 Nov 2009 16:35:25 -0500 Message-ID: <4B01C59A.9050507@sgi.com> Date: Mon, 16 Nov 2009 13:35:22 -0800 From: Mike Travis User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Ingo Molnar CC: Thomas Gleixner , Andrew Morton , Heiko Carstens , Roland Dreier , Randy Dunlap , Tejun Heo , Andi Kleen , Greg Kroah-Hartman , Yinghai Lu , "H. Peter Anvin" , David Rientjes , Steven Rostedt , Rusty Russell , Hidetoshi Seto , Jack Steiner , Frederic Weisbecker , x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/6] x86: Limit the number of per cpu MCE bootup messages References: <20091116210718.412792000@alcatraz.americas.sgi.com> <20091116210727.456553000@alcatraz.americas.sgi.com> <20091116212251.GB2221@elte.hu> In-Reply-To: <20091116212251.GB2221@elte.hu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 705 Lines: 28 Ingo Molnar wrote: > * Mike Travis wrote: > >> @@ -83,6 +86,7 @@ >> unsigned long flags; >> int hdr = 0; >> int i; >> + char buf[120]; > > that constant is not particularly nice, is it? > > Ingo I'm up for suggestions. I just noticed that during testing, the MCE Banks messages overflowed 80 chars but I didn't actually check to see what the longest might be. Should I trim it to 80? Or use a different constant? Thanks, Mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/