From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: axboe@kernel.dk, hch@infradead.org, tytso@mit.edu,
martin.petersen@oracle.com, snitzer@redhat.com,
linux-api@vger.kernel.org, bfoster@redhat.com, xfs@oss.sgi.com,
linux-block@vger.kernel.org, dm-devel@redhat.com,
linux-fsdevel@vger.kernel.org, bart.vanassche@sandisk.com
Subject: Re: [PATCH v10 0/3] fallocate for block devices
Date: Thu, 25 Aug 2016 22:15:52 -0400 [thread overview]
Message-ID: <yq1shtsb7hj.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <147216972158.7860.13484490862091226290.stgit@birch.djwong.org> (Darrick J. Wong's message of "Thu, 25 Aug 2016 17:02:01 -0700")
>>>>> "Darrick" == Darrick J Wong <darrick.wong@oracle.com> writes:
Darrick,
Darrick> This is a redesign of the patch series that fixes various
Darrick> interface problems with the existing "zero out this part of a
Darrick> block device" code. BLKZEROOUT2 is gone.
Looks good to me. Let's get this merged. Pretty please!
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org, tytso@mit.edu,
martin.petersen@oracle.com, snitzer@redhat.com,
linux-api@vger.kernel.org, bfoster@redhat.com, xfs@oss.sgi.com,
hch@infradead.org, dm-devel@redhat.com,
linux-fsdevel@vger.kernel.org, bart.vanassche@sandisk.com
Subject: Re: [PATCH v10 0/3] fallocate for block devices
Date: Thu, 25 Aug 2016 22:15:52 -0400 [thread overview]
Message-ID: <yq1shtsb7hj.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <147216972158.7860.13484490862091226290.stgit@birch.djwong.org> (Darrick J. Wong's message of "Thu, 25 Aug 2016 17:02:01 -0700")
>>>>> "Darrick" == Darrick J Wong <darrick.wong@oracle.com> writes:
Darrick,
Darrick> This is a redesign of the patch series that fixes various
Darrick> interface problems with the existing "zero out this part of a
Darrick> block device" code. BLKZEROOUT2 is gone.
Looks good to me. Let's get this merged. Pretty please!
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-08-26 2:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 0:02 [PATCH v10 0/3] fallocate for block devices Darrick J. Wong
2016-08-26 0:02 ` Darrick J. Wong
2016-08-26 0:02 ` [PATCH 1/3] block: invalidate the page cache when issuing BLKZEROOUT Darrick J. Wong
2016-08-26 0:02 ` Darrick J. Wong
2016-08-26 0:02 ` [PATCH 2/3] block: require write_same and discard requests align to logical block size Darrick J. Wong
2016-08-26 0:02 ` Darrick J. Wong
2016-08-26 0:02 ` [PATCH 3/3] block: implement (some of) fallocate for block devices Darrick J. Wong
2016-08-26 0:02 ` Darrick J. Wong
2016-08-26 2:15 ` Martin K. Petersen [this message]
2016-08-26 2:15 ` [PATCH v10 0/3] " Martin K. Petersen
2016-09-29 0:39 Darrick J. Wong
2016-09-29 0:39 ` 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=yq1shtsb7hj.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@sandisk.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=tytso@mit.edu \
--cc=xfs@oss.sgi.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 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.