From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, linux-scsi@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
philipp.reisner@linbit.com, linux-block@vger.kernel.org,
dm-devel@redhat.com, target-devel@vger.kernel.org,
lars.ellenberg@linbit.com, drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] remove REQ_OP_WRITE_SAME
Date: Mon, 08 May 2017 22:06:30 -0400 [thread overview]
Message-ID: <yq1efvyss0p.fsf@oracle.com> (raw)
In-Reply-To: <20170505085713.GA5008@lst.de> (Christoph Hellwig's message of "Fri, 5 May 2017 10:57:13 +0200")
Christoph,
> Any chance to get a sneak preview of that work?
I have been on the road since LSF/MM and just got back home. I'll make
it a priority.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-05-09 2:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 8:48 [Drbd-dev] remove REQ_OP_WRITE_SAME Christoph Hellwig
2017-04-12 8:48 ` [Drbd-dev] [PATCH 1/8] drbd: drop REQ_OP_WRITE_SAME support Christoph Hellwig
2017-04-12 8:48 ` [Drbd-dev] [PATCH 2/8] target/iblock: convert WRITE_SAME to blkdev_issue_zeroout Christoph Hellwig
2017-04-12 8:48 ` [Drbd-dev] [PATCH 3/8] sd: remove write same support Christoph Hellwig
2017-04-12 8:48 ` [Drbd-dev] [PATCH 4/8] md: drop WRITE_SAME support Christoph Hellwig
2017-04-12 8:48 ` [Drbd-dev] [PATCH 5/8] dm: remove write same support Christoph Hellwig
2017-04-12 8:48 ` [Drbd-dev] [PATCH 6/8] block: remove REQ_OP_WRITE_SAME support Christoph Hellwig
2017-04-12 8:48 ` [Drbd-dev] [PATCH 7/8] block: remove bio_no_advance_iter Christoph Hellwig
2017-04-12 8:48 ` [Drbd-dev] [PATCH 8/8] block: use bio_has_data to check if a bio has bvecs Christoph Hellwig
2017-04-14 2:23 ` [Drbd-dev] remove REQ_OP_WRITE_SAME Martin K. Petersen
2017-05-05 8:57 ` Christoph Hellwig
2017-05-09 2:06 ` Martin K. Petersen [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=yq1efvyss0p.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=drbd-dev@lists.linbit.com \
--cc=hch@lst.de \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=philipp.reisner@linbit.com \
--cc=target-devel@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