All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] quiet MMCONFIG related printks
Date: Wed, 3 Jan 2007 09:20:49 -0800	[thread overview]
Message-ID: <200701030920.49991.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <1167832386.3095.20.camel@laptopd505.fenrus.org>

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

      parent reply	other threads:[~2007-01-03 17:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02  5:01 [PATCH] quiet MMCONFIG related printks Jesse Barnes
2007-01-02 10:36 ` Alan
2007-01-02 16:37   ` Jesse Barnes
2007-01-03 13:52   ` Arjan van de Ven
2007-01-03 13:53 ` Arjan van de Ven
2007-01-03 16:49   ` Jesse Barnes
2007-01-03 17:01     ` Arjan van de Ven
2007-01-03 19:29       ` Stephen Clark
2007-01-03 17:20   ` Jesse Barnes [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200701030920.49991.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.