From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
agruenba@redhat.com
Subject: Re: [PATCH 8/8] iomap: move internal declarations into fs/iomap/
Date: Wed, 17 Jul 2019 07:53:17 -0700 [thread overview]
Message-ID: <20190717145317.GC7093@magnolia> (raw)
In-Reply-To: <20190717062231.GB27285@infradead.org>
On Tue, Jul 16, 2019 at 11:22:31PM -0700, Christoph Hellwig wrote:
> On Tue, Jul 16, 2019 at 10:59:48PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Move internal function declarations out of fs/internal.h into
> > include/linux/iomap.h so that our transition is complete.
> >
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
>
> Didn't I ack this earlier?
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
<urk> Yep, sorry, it was late. Fixed. :/
--D
prev parent reply other threads:[~2019-07-17 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 5:58 [PATCH v3 0/8] iomap: regroup code by functional area Darrick J. Wong
2019-07-17 5:59 ` [PATCH 1/8] iomap: start moving code to fs/iomap/ Darrick J. Wong
2019-07-17 6:22 ` Christoph Hellwig
2019-07-17 5:59 ` [PATCH 2/8] iomap: move the swapfile code into a separate file Darrick J. Wong
2019-07-17 5:59 ` [PATCH 3/8] iomap: move the file mapping reporting " Darrick J. Wong
2019-07-17 5:59 ` [PATCH 4/8] iomap: move the SEEK_HOLE " Darrick J. Wong
2019-07-17 5:59 ` [PATCH 5/8] iomap: move the direct IO " Darrick J. Wong
2019-07-17 5:59 ` [PATCH 6/8] iomap: move the buffered " Darrick J. Wong
2019-07-17 5:59 ` [PATCH 7/8] iomap: move the main iteration " Darrick J. Wong
2019-07-17 5:59 ` [PATCH 8/8] iomap: move internal declarations into fs/iomap/ Darrick J. Wong
2019-07-17 6:22 ` Christoph Hellwig
2019-07-17 14:53 ` 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=20190717145317.GC7093@magnolia \
--to=darrick.wong@oracle.com \
--cc=agruenba@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.