Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030327AbWAaEPY (ORCPT ); Mon, 30 Jan 2006 23:15:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030223AbWAaEPY (ORCPT ); Mon, 30 Jan 2006 23:15:24 -0500 Received: from smtp-3.llnl.gov ([128.115.41.83]:2010 "EHLO smtp-3.llnl.gov") by vger.kernel.org with ESMTP id S1030224AbWAaEPX (ORCPT ); Mon, 30 Jan 2006 23:15:23 -0500 From: Dave Peterson To: ebiederman@lnxi.com (Eric W. Biederman) Subject: Re: noisy edac Date: Mon, 30 Jan 2006 20:15:13 -0800 User-Agent: KMail/1.5.3 Cc: Gunther Mayer , "bluesmoke-devel@lists.sourceforge.net" , Linux Kernel References: <20060130185931.71975.qmail@web50112.mail.yahoo.com> <200601301653.15984.dsp@llnl.gov> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601302015.13057.dsp@llnl.gov> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 804 Lines: 16 On Monday 30 January 2006 19:22, Eric W. Biederman wrote: > One piece missing from this conversation is the issue that we need errors > in a uniform format. That is why edac_mc has helper functions. > > However there will always be errors that don't fit any particular model. > Could we add a edac_printk(dev, ); That is similar to dev_printk but > prints out an EDAC header and the device on which the error was found? > Letting the rest of the string be user specified. I like this idea. It would facilitate grepping in logfiles for EDAC-related errors. - 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/