From: Christoph Hellwig <hch@infradead.org>
To: Zorro Lang <zlang@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>, Chao Yu <chao@kernel.org>,
Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] common/rc: support f2fs in _require_fanotify_ioerrors()
Date: Tue, 31 Mar 2026 23:19:56 -0700 [thread overview]
Message-ID: <acy5DBohMXkFXd-_@infradead.org> (raw)
In-Reply-To: <20260331201105.xxjmqfne4rckc26b@doltdoltdolt>
On Wed, Apr 01, 2026 at 04:11:05AM +0800, Zorro Lang wrote:
> On Tue, Mar 24, 2026 at 10:53:01PM -0700, Christoph Hellwig wrote:
> > On Tue, Mar 24, 2026 at 10:56:55AM +0800, Chao Yu wrote:
> > > This patch allows to run generic/791 on f2fs.
> >
> > When was this introduced? This doesn't currently exist in mainline,
>
> Hi Christoph,
>
> g/791 and _require_fanotify_ioerrors was introduced in v2026.03.20.
I mean the f2fs kernel support, sorry.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Zorro Lang <zlang@redhat.com>
Cc: Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@infradead.org>,
jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH] common/rc: support f2fs in _require_fanotify_ioerrors()
Date: Tue, 31 Mar 2026 23:19:56 -0700 [thread overview]
Message-ID: <acy5DBohMXkFXd-_@infradead.org> (raw)
In-Reply-To: <20260331201105.xxjmqfne4rckc26b@doltdoltdolt>
On Wed, Apr 01, 2026 at 04:11:05AM +0800, Zorro Lang wrote:
> On Tue, Mar 24, 2026 at 10:53:01PM -0700, Christoph Hellwig wrote:
> > On Tue, Mar 24, 2026 at 10:56:55AM +0800, Chao Yu wrote:
> > > This patch allows to run generic/791 on f2fs.
> >
> > When was this introduced? This doesn't currently exist in mainline,
>
> Hi Christoph,
>
> g/791 and _require_fanotify_ioerrors was introduced in v2026.03.20.
I mean the f2fs kernel support, sorry.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-04-01 6:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 2:56 [PATCH] common/rc: support f2fs in _require_fanotify_ioerrors() Chao Yu
2026-03-24 2:56 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-03-25 5:53 ` Christoph Hellwig
2026-03-25 5:53 ` [f2fs-dev] " Christoph Hellwig
2026-03-25 6:30 ` Chao Yu
2026-03-25 6:30 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-03-31 20:11 ` Zorro Lang
2026-03-31 20:11 ` [f2fs-dev] " Zorro Lang via Linux-f2fs-devel
2026-04-01 6:19 ` Christoph Hellwig [this message]
2026-04-01 6:19 ` Christoph Hellwig
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=acy5DBohMXkFXd-_@infradead.org \
--to=hch@infradead.org \
--cc=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zlang@kernel.org \
--cc=zlang@redhat.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 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.