linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Behrens <sbehrens@giantdisaster.de>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] Btrfs: remove unwanted kernel log output
Date: Tue, 17 Jul 2012 17:02:09 +0200	[thread overview]
Message-ID: <cover.1342534465.git.sbehrens@giantdisaster.de> (raw)

People complained about unwanted kernel log output at mount time,
related to btrfs device I/O statistics. With these two commits, the
two messages are removed or filtered, respectively.

Stefan Behrens (2):
  Btrfs: remove unwanted printk() for btrfs device I/O stats
  Btrfs: suppress printk() if all device I/O stats are zero

 fs/btrfs/volumes.c | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

-- 
1.7.11.2


             reply	other threads:[~2012-07-17 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 15:02 Stefan Behrens [this message]
2012-07-17 15:02 ` [PATCH 1/2] Btrfs: remove unwanted printk() for btrfs device I/O stats Stefan Behrens
2012-07-17 15:02 ` [PATCH 2/2] Btrfs: suppress printk() if all device I/O stats are zero Stefan Behrens

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=cover.1342534465.git.sbehrens@giantdisaster.de \
    --to=sbehrens@giantdisaster.de \
    --cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).