From: Christian Brauner <brauner@kernel.org>
To: "陈涛涛 Taotao Chen" <chentaotao@didiglobal.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-block@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
chentao325@qq.com, frank.li@vivo.com,
kernel test robot <lkp@intel.com>,
tytso@mit.edu, hch@infradead.org, adilger.kernel@dilger.ca,
willy@infradead.org, jani.nikula@linux.intel.com,
rodrigo.vivi@intel.com, tursulin@ursulin.net, airlied@gmail.com
Subject: Re: [PATCH v6 0/5] fs: refactor write_begin/write_end and add ext4 IOCB_DONTCACHE support
Date: Wed, 16 Jul 2025 14:50:04 +0200 [thread overview]
Message-ID: <20250716-reinigen-kleiden-c6bca9969819@brauner> (raw)
In-Reply-To: <20250716093559.217344-1-chentaotao@didiglobal.com>
On Wed, 16 Jul 2025 09:36:01 +0000, 陈涛涛 Taotao Chen wrote:
> From: Taotao Chen <chentaotao@didiglobal.com>
>
> This patch series refactors the address_space_operations write_begin()
> and write_end() callbacks to take const struct kiocb * as their first
> argument, allowing IOCB flags such as IOCB_DONTCACHE to propagate to the
> filesystem's buffered I/O path.
>
> [...]
Applied to the vfs-6.17.misc branch of the vfs/vfs.git tree.
Patches in the vfs-6.17.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.17.misc
[1/5] drm/i915: Use kernel_write() in shmem object create
https://git.kernel.org/vfs/vfs/c/e7b840fd4956
[2/5] drm/i915: Refactor shmem_pwrite() to use kiocb and write_iter
https://git.kernel.org/vfs/vfs/c/048832a3f400
[3/5] fs: change write_begin/write_end interface to take struct kiocb *
https://git.kernel.org/vfs/vfs/c/e9d8e2bf2320
[4/5] mm/pagemap: add write_begin_get_folio() helper function
https://git.kernel.org/vfs/vfs/c/b799474b9aeb
[5/5] ext4: support uncached buffered I/O
https://git.kernel.org/vfs/vfs/c/ae21c0c0ac56
prev parent reply other threads:[~2025-07-16 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 9:36 陈涛涛 Taotao Chen
2025-07-16 9:36 ` [PATCH v6 1/5] drm/i915: Use kernel_write() in shmem object create 陈涛涛 Taotao Chen
2025-07-16 9:36 ` [PATCH v6 2/5] drm/i915: Refactor shmem_pwrite() to use kiocb and write_iter 陈涛涛 Taotao Chen
2025-07-16 9:36 ` [PATCH v6 3/5] fs: change write_begin/write_end interface to take struct kiocb * 陈涛涛 Taotao Chen
2025-07-16 9:36 ` [PATCH v6 4/5] mm/pagemap: add write_begin_get_folio() helper function 陈涛涛 Taotao Chen
2025-07-16 9:36 ` [PATCH v6 5/5] ext4: support uncached buffered I/O 陈涛涛 Taotao Chen
2025-07-16 12:50 ` Christian Brauner [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=20250716-reinigen-kleiden-c6bca9969819@brauner \
--to=brauner@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=airlied@gmail.com \
--cc=chentao325@qq.com \
--cc=chentaotao@didiglobal.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank.li@vivo.com \
--cc=hch@infradead.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tursulin@ursulin.net \
--cc=tytso@mit.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