From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/2] xfs: clean up xfs_file_iomap_begin()
Date: Thu, 3 May 2018 16:19:32 -0700 [thread overview]
Message-ID: <20180503231932.GF26569@magnolia> (raw)
In-Reply-To: <20180502055144.28851-1-david@fromorbit.com>
On Wed, May 02, 2018 at 03:51:42PM +1000, Dave Chinner wrote:
> Hi folks,
>
> These patches follow up on recent changes to the locking and
> non-blocking behaviour of xfs_file_iomap_begin() to make it easier
> to follow and understand. The code is a bit of a tangle right now,
> and these two patches pull all of the locking and NOWAIT decisions
> into a single function and out of all the mapping code.
>
> There are no functional changes here, just a code re-org.
Looks ok, will test...
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
>
> Cheers,
>
> Dave.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-05-03 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 5:51 [PATCH 0/2] xfs: clean up xfs_file_iomap_begin() Dave Chinner
2018-05-02 5:51 ` [PATCH 1/2] xfs: simplify xfs_file_iomap_begin() logic Dave Chinner
2018-05-07 14:41 ` Christoph Hellwig
2018-05-02 5:51 ` [PATCH 2/2] xfs: clean up locking in xfs_file_iomap_begin Dave Chinner
2018-05-07 14:44 ` Christoph Hellwig
2018-05-02 12:31 ` [PATCH 0/2] xfs: clean up xfs_file_iomap_begin() Carlos Maiolino
2018-05-03 23:19 ` Darrick J. Wong [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=20180503231932.GF26569@magnolia \
--to=darrick.wong@oracle.com \
--cc=david@fromorbit.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