From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Andreas Gruenbacher <agruenba@redhat.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>, Jan Kara <jack@suse.cz>,
mbobrowski@mbobrowski.org, riteshh@linux.ibm.com
Subject: Re: [ANNOUNCE] xfs-linux: iomap-for-next updated to b7b293bdaaf4
Date: Sat, 19 Oct 2019 01:13:45 -0700 [thread overview]
Message-ID: <20191019081345.GB21691@infradead.org> (raw)
In-Reply-To: <20191019012635.GC6719@magnolia>
On Fri, Oct 18, 2019 at 06:26:35PM -0700, Darrick J. Wong wrote:
> Dave Chinner (1):
> [8a23414ee345] iomap: iomap that extends beyond EOF should be marked dirty
I think this one if 5.4/-stable material.
prev parent reply other threads:[~2019-10-19 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 1:26 [ANNOUNCE] xfs-linux: iomap-for-next updated to b7b293bdaaf4 Darrick J. Wong
2019-10-19 8:13 ` Christoph Hellwig [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=20191019081345.GB21691@infradead.org \
--to=hch@infradead.org \
--cc=Damien.LeMoal@wdc.com \
--cc=agruenba@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mbobrowski@mbobrowski.org \
--cc=riteshh@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).