From: Jens Axboe <axboe@kernel.dk>
To: relliott@beardog.cce.hp.com, Robert Elliott <elliott@hp.com>
Cc: webbnh@hp.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
scameron@beardog.cce.hp.com
Subject: Re: [PATCH 0/2] fs: merge I/O error prints into one line
Date: Mon, 20 Oct 2014 16:01:40 -0600 [thread overview]
Message-ID: <54458644.5000404@kernel.dk> (raw)
In-Reply-To: <544585FE.7080604@kernel.dk>
On 10/20/2014 04:00 PM, Jens Axboe wrote:
> On 10/20/2014 03:43 PM, relliott@beardog.cce.hp.com wrote:
>> On Wed, Aug 27, 2014 at 10:51:54AM -0500, Robert Elliott wrote:
>>> The following series merges I/O error prints into one
>>> line and makes rate limited messages clearer.
>>>
>>> ---
>>>
>>> Robert Elliott (2):
>>> fs: merge I/O error prints into one line
>>> fs: clarify rate limit suppressed buffer I/O errors
>>>
>>>
>>> fs/buffer.c | 38 +++++++++-----------------------------
>>> 1 files changed, 9 insertions(+), 29 deletions(-)
>>>
>>> --
>>> Rob Elliott, HP Server Storage elliott@hp.com
>>
>> ping
>
> Both are in 3.18-rc1, as released yesterday.
Ugh no, I mixed these up with the other two (related) patches. I'll add
these for a later pull this cycle.
--
Jens Axboe
prev parent reply other threads:[~2014-10-20 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 15:51 [PATCH 0/2] fs: merge I/O error prints into one line Robert Elliott
2014-08-27 15:51 ` [PATCH 1/2] " Robert Elliott
2014-08-27 15:52 ` [PATCH 2/2] fs: clarify rate limit suppressed buffer I/O errors Robert Elliott
2014-10-20 21:43 ` [PATCH 0/2] fs: merge I/O error prints into one line relliott
2014-10-20 22:00 ` Jens Axboe
2014-10-20 22:01 ` Jens Axboe [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=54458644.5000404@kernel.dk \
--to=axboe@kernel.dk \
--cc=elliott@hp.com \
--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).