From: Johannes Thumshirn <jthumshirn@suse.de>
To: linux-nvdimm@lists.01.org
Subject: Re: [PATCH] libnvdimm, blk: quiet i/o error reporting
Date: Tue, 29 Mar 2016 09:56:00 +0200 [thread overview]
Message-ID: <2224391.CcK4bhtD8T@c203> (raw)
In-Reply-To: <20160325215310.31923.81368.stgit@dwillia2-desk3.jf.intel.com>
On Freitag, 25. März 2016 14:59:41 CEST Dan Williams wrote:
> I/O errors events have the potential to be a high frequency and a log
> message for each event can swamp the system. This message is also
> redundant with upper layer error reporting.
>
> Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Looks good to me,
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2016-03-29 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 21:59 [PATCH] libnvdimm, blk: quiet i/o error reporting Dan Williams
2016-03-28 14:40 ` Elliott, Robert (Persistent Memory)
2016-03-28 23:57 ` Dan Williams
2016-03-29 7:56 ` Johannes Thumshirn [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=2224391.CcK4bhtD8T@c203 \
--to=jthumshirn@suse.de \
--cc=linux-nvdimm@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.