From: patchwork-bot+f2fs@kernel.org
To: Matthew Wilcox <willy@infradead.org>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/6] Remove page_mapping()
Date: Mon, 20 May 2024 21:16:46 +0000 [thread overview]
Message-ID: <171623980648.27511.9576243592130521184.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240423225552.4113447-1-willy@infradead.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Andrew Morton <akpm@linux-foundation.org>:
On Tue, 23 Apr 2024 23:55:31 +0100 you wrote:
> There are only a few users left. Convert them all to either call
> folio_mapping() or just use folio->mapping directly.
>
> Matthew Wilcox (Oracle) (6):
> fscrypt: Convert bh_get_inode_and_lblk_num to use a folio
> f2fs: Convert f2fs_clear_page_cache_dirty_tag to use a folio
> memory-failure: Remove calls to page_mapping()
> migrate: Expand the use of folio in __migrate_device_pages()
> userfault; Expand folio use in mfill_atomic_install_pte()
> mm: Remove page_mapping()
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/6] fscrypt: Convert bh_get_inode_and_lblk_num to use a folio
https://git.kernel.org/jaegeuk/f2fs/c/262f014dd7de
- [f2fs-dev,2/6] f2fs: Convert f2fs_clear_page_cache_dirty_tag to use a folio
https://git.kernel.org/jaegeuk/f2fs/c/196ad49cd626
- [f2fs-dev,3/6] memory-failure: Remove calls to page_mapping()
https://git.kernel.org/jaegeuk/f2fs/c/89f5c54b2281
- [f2fs-dev,4/6] migrate: Expand the use of folio in __migrate_device_pages()
https://git.kernel.org/jaegeuk/f2fs/c/e18a9faf06c2
- [f2fs-dev,5/6] userfault; Expand folio use in mfill_atomic_install_pte()
https://git.kernel.org/jaegeuk/f2fs/c/a568b4126b20
- [f2fs-dev,6/6] mm: Remove page_mapping()
(no matching commit)
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:[~2024-05-20 21:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 22:55 Matthew Wilcox (Oracle)
2024-04-23 22:55 ` [PATCH 1/6] fscrypt: Convert bh_get_inode_and_lblk_num to use a folio Matthew Wilcox (Oracle)
2024-04-23 23:34 ` Eric Biggers
2024-04-23 22:55 ` [PATCH 2/6] f2fs: Convert f2fs_clear_page_cache_dirty_tag " Matthew Wilcox (Oracle)
2024-04-24 11:53 ` David Hildenbrand
2024-04-23 22:55 ` [PATCH 3/6] memory-failure: Remove calls to page_mapping() Matthew Wilcox (Oracle)
2024-04-23 23:52 ` Sidhartha Kumar
2024-04-24 11:54 ` David Hildenbrand
2024-04-25 6:21 ` Miaohe Lin
2024-04-23 22:55 ` [PATCH 4/6] migrate: Expand the use of folio in __migrate_device_pages() Matthew Wilcox (Oracle)
2024-04-24 11:54 ` David Hildenbrand
2024-04-23 22:55 ` [PATCH 5/6] userfault; Expand folio use in mfill_atomic_install_pte() Matthew Wilcox (Oracle)
2024-04-24 11:55 ` David Hildenbrand
2024-04-23 22:55 ` [PATCH 6/6] mm: Remove page_mapping() Matthew Wilcox (Oracle)
2024-04-24 11:55 ` David Hildenbrand
2024-04-24 23:34 ` Andrew Morton
2024-04-24 23:59 ` Matthew Wilcox
2024-05-20 21:16 ` patchwork-bot+f2fs [this message]
2024-07-24 2:16 ` [f2fs-dev] [PATCH 0/6] " patchwork-bot+f2fs
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=171623980648.27511.9576243592130521184.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox