From: Christoph Hellwig <hch@lst.de>
To: Kundan Kumar <kundan.kumar@samsung.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, agruenba@redhat.com,
trondmy@kernel.org, anna@kernel.org, hch@lst.de,
brauner@kernel.org, jack@suse.cz, viro@zeniv.linux.org.uk,
djwong@kernel.org, jlayton@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, gfs2@lists.linux.dev,
linux-nfs@vger.kernel.org, gost.dev@samsung.com,
anuj20.g@samsung.com, vishak.g@samsung.com, joshi.k@samsung.com
Subject: Re: [PATCH v2 0/4] Avoid filesystem references to writeback internals
Date: Fri, 13 Feb 2026 07:24:35 +0100 [thread overview]
Message-ID: <20260213062435.GA27228@lst.de> (raw)
In-Reply-To: <20260213054634.79785-1-kundan.kumar@samsung.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-02-13 6:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260213055123epcas5p25f52d5961c04b1a1f514827a494a0773@epcas5p2.samsung.com>
2026-02-13 5:46 ` [PATCH v2 0/4] Avoid filesystem references to writeback internals Kundan Kumar
2026-02-13 5:46 ` [PATCH v2 1/4] writeback: prep helpers for dirty-limit and writeback accounting Kundan Kumar
2026-02-13 5:46 ` [PATCH v2 2/4] f2fs: stop using writeback internals for dirty_exceeded checks Kundan Kumar
2026-02-13 5:46 ` [PATCH v2 3/4] gfs2: stop using writeback internals for dirty_exceeded check Kundan Kumar
2026-02-13 5:46 ` [PATCH v2 4/4] nfs: stop using writeback internals for WB_WRITEBACK accounting Kundan Kumar
2026-02-13 6:24 ` Christoph Hellwig [this message]
2026-02-17 12:26 ` [PATCH v2 0/4] Avoid filesystem references to writeback internals Christian Brauner
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=20260213062435.GA27228@lst.de \
--to=hch@lst.de \
--cc=agruenba@redhat.com \
--cc=anna@kernel.org \
--cc=anuj20.g@samsung.com \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=djwong@kernel.org \
--cc=gfs2@lists.linux.dev \
--cc=gost.dev@samsung.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=jlayton@kernel.org \
--cc=joshi.k@samsung.com \
--cc=kundan.kumar@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=vishak.g@samsung.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