From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
brauner@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 05/10] f2fs: Use folio_next_pos()
Date: Tue, 09 Dec 2025 17:18:49 +0000 [thread overview]
Message-ID: <176530072903.4018985.4925454806084370297.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251024170822.1427218-6-willy@infradead.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Christian Brauner <brauner@kernel.org>:
On Fri, 24 Oct 2025 18:08:13 +0100 you wrote:
> This is one instruction more efficient than open-coding folio_pos() +
> folio_size(). It's the equivalent of (x + y) << z rather than
> x << z + y << z.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> Cc: Jaegeuk Kim <jaegeuk@kernel.org>
> Cc: Chao Yu <chao@kernel.org>
> Cc: linux-f2fs-devel@lists.sourceforge.net
>
> [...]
Here is the summary with links:
- [f2fs-dev,05/10] f2fs: Use folio_next_pos()
https://git.kernel.org/jaegeuk/f2fs/c/4fcafa30b70a
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
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, brauner@kernel.org,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 05/10] f2fs: Use folio_next_pos()
Date: Tue, 09 Dec 2025 17:18:49 +0000 [thread overview]
Message-ID: <176530072903.4018985.4925454806084370297.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251024170822.1427218-6-willy@infradead.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Christian Brauner <brauner@kernel.org>:
On Fri, 24 Oct 2025 18:08:13 +0100 you wrote:
> This is one instruction more efficient than open-coding folio_pos() +
> folio_size(). It's the equivalent of (x + y) << z rather than
> x << z + y << z.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> Cc: Jaegeuk Kim <jaegeuk@kernel.org>
> Cc: Chao Yu <chao@kernel.org>
> Cc: linux-f2fs-devel@lists.sourceforge.net
>
> [...]
Here is the summary with links:
- [f2fs-dev,05/10] f2fs: Use folio_next_pos()
https://git.kernel.org/jaegeuk/f2fs/c/4fcafa30b70a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-12-09 17:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 17:08 [PATCH 00/10] Add and use folio_next_pos() Matthew Wilcox (Oracle)
2025-10-24 17:08 ` [PATCH 01/10] filemap: Add folio_next_pos() Matthew Wilcox (Oracle)
2025-10-27 7:53 ` Christoph Hellwig
2025-10-27 8:33 ` Joseph Qi
2025-10-24 17:08 ` [PATCH 02/10] btrfs: Use folio_next_pos() Matthew Wilcox (Oracle)
2025-10-30 18:14 ` David Sterba
2025-10-24 17:08 ` [PATCH 03/10] buffer: " Matthew Wilcox (Oracle)
2025-10-27 7:54 ` Christoph Hellwig
2025-10-30 9:35 ` Jan Kara
2025-10-24 17:08 ` [PATCH 04/10] ext4: " Matthew Wilcox (Oracle)
2025-10-25 3:20 ` Zhang Yi
2025-10-27 7:54 ` Christoph Hellwig
2025-10-24 17:08 ` [f2fs-dev] [PATCH 05/10] f2fs: " Matthew Wilcox (Oracle)
2025-10-24 17:08 ` Matthew Wilcox (Oracle)
2025-10-27 11:57 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-10-27 11:57 ` Chao Yu
2025-12-09 17:18 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-12-09 17:18 ` [f2fs-dev] " patchwork-bot+f2fs
2025-10-24 17:08 ` [PATCH 06/10] gfs2: " Matthew Wilcox (Oracle)
2025-10-24 17:08 ` [PATCH 07/10] iomap: " Matthew Wilcox (Oracle)
2025-10-24 17:10 ` Darrick J. Wong
2025-10-27 7:53 ` Christoph Hellwig
2025-10-24 17:08 ` [PATCH 08/10] netfs: " Matthew Wilcox (Oracle)
2025-10-24 17:36 ` Paulo Alcantara
2025-10-27 14:16 ` David Howells
2025-10-27 14:50 ` Matthew Wilcox
2025-10-24 17:08 ` [PATCH 09/10] xfs: " Matthew Wilcox (Oracle)
2025-10-27 7:53 ` Christoph Hellwig
2025-10-24 17:08 ` [PATCH 10/10] mm: " Matthew Wilcox (Oracle)
2025-10-27 7:54 ` Christoph Hellwig
2025-10-27 15:43 ` David Hildenbrand
2025-11-08 5:00 ` Matthew Wilcox
2025-11-11 9:59 ` Christian Brauner
2025-10-31 12:12 ` [PATCH 00/10] Add and use folio_next_pos() 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=176530072903.4018985.4925454806084370297.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=brauner@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=willy@infradead.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.