From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [PATCH 2/8] ACPI, CPER: Update cper info Date: Tue, 15 Oct 2013 18:57:18 -0700 Message-ID: <1381888638.22110.43.camel@joe-AO722> References: <1381473166-29303-1-git-send-email-gong.chen@linux.intel.com> <1381473166-29303-3-git-send-email-gong.chen@linux.intel.com> <20131011090630.GB5925@pd.tnic> <20131011154759.GJ5925@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from smtprelay0038.hostedemail.com ([216.40.44.38]:56448 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751147Ab3JPB5W (ORCPT ); Tue, 15 Oct 2013 21:57:22 -0400 In-Reply-To: <20131011154759.GJ5925@pd.tnic> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Borislav Petkov Cc: "Chen, Gong" , tony.luck@intel.com, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org On Fri, 2013-10-11 at 17:47 +0200, Borislav Petkov wrote: > On Fri, Oct 11, 2013 at 11:06:30AM +0200, Borislav Petkov wrote: > > > - printk("%s""APEI generic hardware error status\n", pfx); > > > + printk("%s""Generic Hardware Error Status\n", pfx); > > > > Btw, what's the story with printk not using KERN_x levels in this file? > > Why are we falling back to default printk levels for all printks here > > and shouldn't we rather prioritize them by urgency into, say, KERN_ERR, > > KERN_INFO, etc? > > Ignore that - checkpatch complained about it but I kinda missed that > we're handing down the prefix. I think it'd be better to rename pfx to level as that's what printk.h calls them.