From: Christoph Hellwig <hch@infradead.org>
To: Yang Erkun <yangerkun@huawei.com>
Cc: hch@infradead.org, zlang@kernel.org, fstests@vger.kernel.org,
linux-mm@kvack.org, hughd@google.com, akpm@linux-foundation.org,
yoyang@redhat.com
Subject: Re: [PATCH v2 2/2] generic/732: don't run it on tmpfs
Date: Mon, 29 Jul 2024 07:16:28 -0700 [thread overview]
Message-ID: <ZqekPERYzP93HacM@infradead.org> (raw)
In-Reply-To: <20240729084715.1736839-2-yangerkun@huawei.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2024-07-29 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 8:47 [PATCH v2 1/2] generic/732: remove unused code Yang Erkun
2024-07-29 8:47 ` [PATCH v2 2/2] generic/732: don't run it on tmpfs Yang Erkun
2024-07-29 14:16 ` Christoph Hellwig [this message]
2024-07-29 14:21 ` Chuck Lever III
2024-07-29 14:24 ` Chuck Lever III
2024-07-29 14:30 ` yangerkun
2024-07-29 14:28 ` yangerkun
2024-07-29 14:16 ` [PATCH v2 1/2] generic/732: remove unused code Christoph Hellwig
2024-08-17 6:24 ` yangerkun
2024-08-17 19:16 ` Zorro Lang
2024-08-19 1:06 ` yangerkun
2024-08-19 12:53 ` Zorro Lang
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=ZqekPERYzP93HacM@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=fstests@vger.kernel.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=yangerkun@huawei.com \
--cc=yoyang@redhat.com \
--cc=zlang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.