From: Christoph Hellwig <hch@lst.de>
To: Tal Zussman <tz2294@columbia.edu>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Hannes Reinecke <hare@kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
John Garry <john.garry@linux.dev>,
Christian Brauner <brauner@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Keith Busch <kbusch@kernel.org>,
"Martin K. Petersen" <mkp@kernel.org>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH v6 0/9] block device fixes for large block sizes, IOCB_NOWAIT, and direct I/O
Date: Mon, 12 Oct 2026 14:02:13 +0200 [thread overview]
Message-ID: <20261012120212.GA29154@lst.de> (raw)
In-Reply-To: <20261009-blkdev-fixes-v6-0-307939c387df@columbia.edu>
Still looks good to me in the rebased version.
next prev parent reply other threads:[~2026-10-12 12:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 16:50 Tal Zussman
2026-10-09 16:50 ` [PATCH v6 1/9] block: use iomap_dirty_folio for block devices Tal Zussman
2026-10-09 16:50 ` [PATCH v6 2/9] block: take i_rwsem for the direct I/O write fallback Tal Zussman
2026-10-09 16:50 ` [PATCH v6 3/9] block: take i_rwsem for the splice read path Tal Zussman
2026-10-09 16:50 ` [PATCH v6 4/9] block: honor IOCB_NOWAIT in the block device buffered " Tal Zussman
2026-10-09 16:50 ` [PATCH v6 5/9] block: fail a short atomic pin in bio_iov_iter_get_pages() Tal Zussman
2026-10-09 16:50 ` [PATCH v6 6/9] block: don't fall back to buffered I/O for atomic writes Tal Zussman
2026-10-09 16:50 ` [PATCH v6 7/9] iomap: reject atomic writes in iomap_file_buffered_write() Tal Zussman
2026-10-09 16:50 ` [PATCH v6 8/9] block: unpin all pages of a bvec in bio_iov_iter_align_down() Tal Zussman
2026-10-09 16:50 ` [PATCH v6 9/9] block: remove dead metadata handling from the async direct I/O path Tal Zussman
2026-10-12 12:02 ` Christoph Hellwig [this message]
2026-10-12 18:51 ` [PATCH v6 0/9] block device fixes for large block sizes, IOCB_NOWAIT, and direct I/O Jens Axboe
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=20261012120212.GA29154@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=hare@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=john.garry@linux.dev \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mkp@kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=tz2294@columbia.edu \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®