From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Bart Van Assche <bvanassche@acm.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 0/4] Reduce the time spent in interrupt context
Date: Tue, 16 Jun 2026 02:50:07 +0000 [thread overview]
Message-ID: <178157820763.407856.9024495873605797681.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1781119949.git.bvanassche@acm.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 10 Jun 2026 12:34:16 -0700 you wrote:
> Hi Jaegeuk,
>
> This patch series reduces the amount of time spent in interrupt context for
> completing write bios. Please consider this patch series for the next merge
> window.
>
> Thanks,
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2,1/4] f2fs: Prepare for supporting delayed bio completion
https://git.kernel.org/jaegeuk/f2fs/c/130a2e41b08d
- [f2fs-dev,v2,2/4] f2fs: Rename f2fs_post_read_wq into f2fs_wq
https://git.kernel.org/jaegeuk/f2fs/c/41e63c48ab9f
- [f2fs-dev,v2,3/4] f2fs: Split f2fs_write_end_io()
https://git.kernel.org/jaegeuk/f2fs/c/09b06dc6a7d5
- [f2fs-dev,v2,4/4] f2fs: Run f2fs_write_end_io() asynchronously
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-06-16 2:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 19:34 [f2fs-dev] [PATCH v2 0/4] Reduce the time spent in interrupt context Bart Van Assche via Linux-f2fs-devel
2026-06-10 19:34 ` [f2fs-dev] [PATCH v2 1/4] f2fs: Prepare for supporting delayed bio completion Bart Van Assche via Linux-f2fs-devel
2026-06-10 19:34 ` [f2fs-dev] [PATCH v2 2/4] f2fs: Rename f2fs_post_read_wq into f2fs_wq Bart Van Assche via Linux-f2fs-devel
2026-06-10 19:34 ` [f2fs-dev] [PATCH v2 3/4] f2fs: Split f2fs_write_end_io() Bart Van Assche via Linux-f2fs-devel
2026-06-10 19:34 ` [f2fs-dev] [PATCH v2 4/4] f2fs: Run f2fs_write_end_io() asynchronously Bart Van Assche via Linux-f2fs-devel
2026-07-28 2:26 ` Chao Yu via Linux-f2fs-devel
2026-06-16 2:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=178157820763.407856.9024495873605797681.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=bvanassche@acm.org \
--cc=jaegeuk@kernel.org \
--cc=patchwork-bot+f2fs@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