From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] quiet MMCONFIG related printks
Date: Wed, 3 Jan 2007 09:20:49 -0800
User-Agent: KMail/1.9.5
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
References: <200701012101.38427.jbarnes@virtuousgeek.org> <1167832386.3095.20.camel@laptopd505.fenrus.org>
In-Reply-To: <1167832386.3095.20.camel@laptopd505.fenrus.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200701030920.49991.jbarnes@virtuousgeek.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1001
Lines: 22

On Wednesday, January 3, 2007 5:53 am, Arjan van de Ven wrote:
> On Mon, 2007-01-01 at 21:01 -0800, Jesse Barnes wrote:
> > Using MMCONFIG for PCI config space access is simply an
> > optimization, not a requirement.  Therefore, when it can't be used,
> > there's no need for KERN_ERR level message.  This patch makes the
> > message a KERN_INFO instead to reduce some of the noise in a kernel
> > boot with the 'quiet' option. (Note that this has no effect on a
> > normal boot, which is ridiculously verbose these days.)
>
> this is wrong, please leave this loud complaint in...

Or maybe the test is just wrong.  I'll try out the PCI MMConfig 
per-chipset patches to see if they work.  That seems like a better long 
term solution anyway.

Thanks,
Jesse
-
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/