From: Eric Sandeen <sandeen@sandeen.net>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/7] xfs_scrub: clean up error level table
Date: Fri, 1 Nov 2019 16:11:05 -0500 [thread overview]
Message-ID: <6fbe07da-2ef6-e1c0-6e32-08bf815b27e7@sandeen.net> (raw)
In-Reply-To: <157177014843.1460394.980952412513737663.stgit@magnolia>
On 10/22/19 1:49 PM, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Rework the error levels table in preparation for adding a few more error
> categories that won't fit on a single line.
Ok, I'll massage this to match my prior reordering.
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
next prev parent reply other threads:[~2019-11-01 21:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 18:48 [PATCH 0/7] xfs_scrub: clean up error classifications Darrick J. Wong
2019-10-22 18:48 ` [PATCH 1/7] xfs_scrub: fix misclassified error reporting Darrick J. Wong
2019-11-01 20:59 ` Eric Sandeen
2019-10-22 18:49 ` [PATCH 2/7] xfs_scrub: simplify post-run reporting logic Darrick J. Wong
2019-11-01 21:05 ` Eric Sandeen
2019-10-22 18:49 ` [PATCH 3/7] xfs_scrub: clean up error level table Darrick J. Wong
2019-11-01 21:11 ` Eric Sandeen [this message]
2019-10-22 18:49 ` [PATCH 4/7] xfs_scrub: explicitly track corruptions, not just errors Darrick J. Wong
2019-11-01 21:15 ` Eric Sandeen
2019-10-22 18:49 ` [PATCH 5/7] xfs_scrub: promote some of the str_info to str_error calls Darrick J. Wong
2019-11-01 21:21 ` Eric Sandeen
2019-10-22 18:49 ` [PATCH 6/7] xfs_scrub: refactor xfs_scrub_excessive_errors Darrick J. Wong
2019-11-01 21:25 ` Eric Sandeen
2019-11-01 21:46 ` Darrick J. Wong
2019-11-01 21:50 ` Eric Sandeen
2019-10-22 18:49 ` [PATCH 7/7] xfs_scrub: create a new category for unfixable errors Darrick J. Wong
2019-11-01 21:32 ` Eric Sandeen
2019-11-01 22:10 ` Darrick J. Wong
2019-11-01 22:15 ` 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=6fbe07da-2ef6-e1c0-6e32-08bf815b27e7@sandeen.net \
--to=sandeen@sandeen.net \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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).