public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Matthew Wilcox <matthew@wil.cx>,
	linux-pci <linux-pci@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: more than 50 percent of dmesg belongs only to PCI and USB
Date: Sat, 14 Mar 2009 08:41:57 -0700	[thread overview]
Message-ID: <20090314154157.GA5864@kroah.com> (raw)
In-Reply-To: <1237016485.2935.12.camel@ht.satnam>

On Sat, Mar 14, 2009 at 01:11:25PM +0530, Jaswinder Singh Rajput wrote:
> Can we make dmesg little bit better and remove some noise and put these
> debug messages on /sys/kernel/debug/ :

Are you sure you don't have some debugging options enabled in your
kernel?

Also, patches gladly accepted :)

thanks,

greg k-h

  reply	other threads:[~2009-03-14 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14  7:41 more than 50 percent of dmesg belongs only to PCI and USB Jaswinder Singh Rajput
2009-03-14 15:41 ` Greg KH [this message]
2009-03-15 23:28 ` Michael Ellerman
2009-03-16  0:39   ` Greg KH
2009-03-16  0:59     ` Michael Ellerman

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=20090314154157.GA5864@kroah.com \
    --to=greg@kroah.com \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox