From: Theodore Ts'o <tytso@mit.edu>
To: Marc Thomas <marc@dragonfly.plus.com>
Cc: linux-ext4@vger.kernel.org, "Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH] e2fsck: fix sparse bmap to extent conversion
Date: Wed, 24 May 2017 22:21:35 -0400 [thread overview]
Message-ID: <20170525022135.tbzsiyd3cbvrdlto@thunk.org> (raw)
In-Reply-To: <982fc176-2a8d-1318-8eec-2524c6af1e00@dragonfly.plus.com>
I've applied this patch to the maint branch (with a slight adjustment
to the expect file for f_convert_bmap_sprase), and then merged it into
the next/master branches (with the adjustment removed), thanks.
I wasn't able see any problems with f_detect_junk, on either the maint
or the next branch. So I'm not sure what issue Marc was seeing there.
- Ted
next prev parent reply other threads:[~2017-05-25 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 19:00 [PATCH] e2fsck: fix sparse bmap to extent conversion Darrick J. Wong
2017-05-24 11:30 ` Marc Thomas
2017-05-25 2:21 ` Theodore Ts'o [this message]
2017-05-25 13:11 ` Marc Thomas
2017-05-25 17:13 ` Theodore Ts'o
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=20170525022135.tbzsiyd3cbvrdlto@thunk.org \
--to=tytso@mit.edu \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=marc@dragonfly.plus.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