From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>,
Andreas Gruenbacher <agruenba@redhat.com>
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to a0e336ba3e3d
Date: Sat, 4 Aug 2018 02:06:19 -0700 [thread overview]
Message-ID: <20180804090619.GA1888@infradead.org> (raw)
In-Reply-To: <20180803191730.GX30972@magnolia>
> Andreas Gruenbacher (6):
> [3d7b6b21f6c5] iomap: mark newly allocated buffer heads as new
> [ebf00be37de3] iomap: complete partial direct I/O writes synchronously
> [19e0c58f6552] iomap: generic inline data handling
> [e184fde6f3f5] iomap: add private pointer to struct iomap
> [ec181f6782d8] iomap: support direct I/O to inline data
> [806a1477b10a] iomap: add inline data support to iomap_readpage_actor
Did you rebase the tree? We really need to keep the iomap base
branch stable as the gfs2 tree is also based on it and we want to avoid
duplicate commits.
next prev parent reply other threads:[~2018-08-04 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 19:17 [ANNOUNCE] xfs-linux: for-next updated to a0e336ba3e3d Darrick J. Wong
2018-08-04 9:06 ` Christoph Hellwig [this message]
2018-08-04 14:25 ` Andreas Gruenbacher
2018-08-05 7:37 ` Christoph Hellwig
2018-08-05 16:08 ` 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=20180804090619.GA1888@infradead.org \
--to=hch@infradead.org \
--cc=agruenba@redhat.com \
--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).