From: Robert Elliott <elliott@hp.com>
To: axboe@kernel.dk, webbnh@hp.com, linux-kernel@vger.kernel.org,
relliott@beardog.cce.hp.com, linux-fsdevel@vger.kernel.org,
viro@zeniv.linux.org.uk, elliott@hp.com,
scameron@beardog.cce.hp.com
Subject: [PATCH 0/2] block: improve I/O error print consistency
Date: Wed, 27 Aug 2014 10:50:25 -0500 [thread overview]
Message-ID: <20140827154628.32075.3821.stgit@beardog.cce.hp.com> (raw)
The following series improves some of the ratelimited
I/O error prints so what is being ratelimited is clearer.
---
Robert Elliott (2):
block: make blk_update_request print prefix match ratelimited prefix
block: include func name in __get_request prints
block/blk-core.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
--
Rob Elliott, HP Server Storage elliott@hp.com
next reply other threads:[~2014-08-27 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 15:50 Robert Elliott [this message]
2014-08-27 15:50 ` [PATCH 1/2] block: make blk_update_request print prefix match ratelimited prefix Robert Elliott
2014-08-27 15:50 ` [PATCH 2/2] block: include func name in __get_request prints Robert Elliott
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=20140827154628.32075.3821.stgit@beardog.cce.hp.com \
--to=elliott@hp.com \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=relliott@beardog.cce.hp.com \
--cc=scameron@beardog.cce.hp.com \
--cc=viro@zeniv.linux.org.uk \
--cc=webbnh@hp.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;
as well as URLs for NNTP newsgroup(s).