From: Dave Chinner <david@fromorbit.com>
To: raghu.prabhu13@gmail.com
Cc: bpm@sgi.com, elder@kernel.org,
Raghavendra D Prabhu <rprabhu@wnohang.net>,
xfs@oss.sgi.com
Subject: Re: [PATCH v3 1/3] xfs: Add ratelimited printk for different alert levels
Date: Mon, 29 Oct 2012 09:05:45 +1100 [thread overview]
Message-ID: <20121028220545.GB4353@dastard> (raw)
In-Reply-To: <ca71153845539b0c76ba3e3aab9611ad6c5cf72b.1348641483.git.rprabhu@wnohang.net>
On Wed, Sep 26, 2012 at 12:26:47PM +0530, raghu.prabhu13@gmail.com wrote:
> From: Raghavendra D Prabhu <rprabhu@wnohang.net>
>
> Ratelimited printk will be useful in printing xfs messages which are otherwise
> not required to be printed always due to their high rate (to prevent kernel ring
> buffer from overflowing), while at the same time required to be printed.
>
> Signed-off-by: Raghavendra D Prabhu <rprabhu@wnohang.net>
This is fine.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-10-28 22:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 6:56 [PATCH v3 0/3] Print when ENOSPC due to lack of inodes raghu.prabhu13
[not found] ` <cover.1348641483.git.rprabhu@wnohang.net>
2012-09-26 6:56 ` [PATCH v3 1/3] xfs: Add ratelimited printk for different alert levels raghu.prabhu13
2012-09-26 6:56 ` [v3 Repost] " Raghavendra D Prabhu
2012-10-26 13:15 ` [v3,1/3] " Rich Johnston
2012-10-28 22:05 ` Dave Chinner [this message]
2013-03-27 14:26 ` [v3 Repost] " Rich Johnston
2013-04-05 18:32 ` Ben Myers
2012-09-26 6:56 ` [PATCH v3 2/3] xfs: Print error when xfs_ialloc_ag_select fails to find continuous free space raghu.prabhu13
2012-10-26 13:15 ` [v3, " Rich Johnston
2012-10-28 22:10 ` [PATCH v3 " Dave Chinner
2012-09-26 6:56 ` [PATCH v3 3/3] xfs: Print error when unable to allocate inodes or out of free inodes raghu.prabhu13
2012-10-26 13:15 ` [v3, " Rich Johnston
2012-10-28 23:21 ` [PATCH v3 " Dave Chinner
2012-10-24 20:56 ` [PATCH v3 0/3] Print when ENOSPC due to lack of inodes Raghavendra Prabhu
2012-10-25 15:23 ` Rich Johnston
2012-10-26 13:18 ` Rich Johnston
2012-10-28 22:05 ` Dave Chinner
2012-10-30 14:59 ` Ben Myers
2012-11-28 2:52 ` Eric Sandeen
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=20121028220545.GB4353@dastard \
--to=david@fromorbit.com \
--cc=bpm@sgi.com \
--cc=elder@kernel.org \
--cc=raghu.prabhu13@gmail.com \
--cc=rprabhu@wnohang.net \
--cc=xfs@oss.sgi.com \
/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