From: Abdifatah Suruur <suruurism@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] fuse: stop stealing pipe pages into the page cache
Date: Wed, 18 Nov 2026 17:14:54 +0300 [thread overview]
Message-ID: <179501129496.10449.5445396291756842907@gmail.com> (raw)
In-Reply-To: <20261118135359.6256-1-suruurism@gmail.com>
Hello,
Please ignore/drop my patch "fuse: stop stealing pipe pages into the page
cache" (message-id <20261118135359.6256-1-suruurism@gmail.com>). After
further checking I found that this issue has already been reported and
fixed upstream by commit 80beb226de50b859913a55be0d6bff9046662294, which
predates my submission. I should have checked the post-snapshot history
more carefully; my patch is redundant. Sorry for the noise.
Thanks,
Abdifatah Suruur
suruurism@gmail.com
prev parent reply other threads:[~2026-11-18 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 13:53 [PATCH] fuse: stop stealing pipe pages into the page cache Abdifatah Suruur
2026-11-18 14:14 ` Abdifatah Suruur [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=179501129496.10449.5445396291756842907@gmail.com \
--to=suruurism@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox