From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: clean up locking in xfs_file_iomap_begin
Date: Mon, 7 May 2018 07:44:34 -0700 [thread overview]
Message-ID: <20180507144434.GB7476@infradead.org> (raw)
In-Reply-To: <20180502055144.28851-3-david@fromorbit.com>
Maybe its because I wrote a lot of the original code, but I really
don't see how this makes thing any more clean.
next prev parent reply other threads:[~2018-05-07 14:44 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 [this message]
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
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=20180507144434.GB7476@infradead.org \
--to=hch@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).