From: Christoph Hellwig <hch@infradead.org>
To: Xueshi Hu <xueshi.hu@smartx.com>
Cc: hch@infradead.org, dan.j.williams@intel.com,
vishal.l.verma@intel.com, dave.jiang@intel.com,
jayalk@intworks.biz, daniel@ffwll.ch, deller@gmx.de,
bcrl@kvack.org, viro@zeniv.linux.org.uk, brauner@kernel.org,
jack@suse.com, tytso@mit.edu, adilger.kernel@dilger.ca,
miklos@szeredi.hu, mike.kravetz@oracle.com,
muchun.song@linux.dev, djwong@kernel.org, willy@infradead.org,
akpm@linux-foundation.org, hughd@google.com,
nvdimm@lists.linux.dev, linux-cxl@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-aio@kvack.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-mm@kvack.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] fs: clean up usage of noop_dirty_folio
Date: Mon, 28 Aug 2023 05:00:52 -0700 [thread overview]
Message-ID: <ZOyMdA/WSZMRWkWY@infradead.org> (raw)
In-Reply-To: <20230828075449.262510-1-xueshi.hu@smartx.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2023-08-28 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 7:54 [PATCH v2] fs: clean up usage of noop_dirty_folio Xueshi Hu
2023-08-28 10:58 ` Jan Kara
2023-08-28 12:00 ` Christoph Hellwig [this message]
2023-08-28 12:18 ` Matthew Wilcox
2023-08-28 14:42 ` Al Viro
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=ZOyMdA/WSZMRWkWY@infradead.org \
--to=hch@infradead.org \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=brauner@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=daniel@ffwll.ch \
--cc=dave.jiang@intel.com \
--cc=deller@gmx.de \
--cc=djwong@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hughd@google.com \
--cc=jack@suse.com \
--cc=jayalk@intworks.biz \
--cc=linux-aio@kvack.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=miklos@szeredi.hu \
--cc=muchun.song@linux.dev \
--cc=nvdimm@lists.linux.dev \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=vishal.l.verma@intel.com \
--cc=willy@infradead.org \
--cc=xueshi.hu@smartx.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).