All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	willy@infradead.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: get rid of buffer_head use
Date: Mon, 05 Aug 2024 23:30:52 +0000	[thread overview]
Message-ID: <172290065219.2803.34268911020752099.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240618072620.720535-1-chao@kernel.org>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Tue, 18 Jun 2024 15:26:20 +0800 you wrote:
> Convert to use folio and related functionality.
> 
> Cc: Matthew Wilcox <willy@infradead.org>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> - support large folio
> - use bd_mapping instead of bd_inode->i_mapping
>  fs/f2fs/data.c  |  1 -
>  fs/f2fs/f2fs.h  | 11 +++++-
>  fs/f2fs/file.c  |  1 -
>  fs/f2fs/inode.c |  1 -
>  fs/f2fs/super.c | 93 +++++++++++++++++++++++++++++--------------------
>  5 files changed, 66 insertions(+), 41 deletions(-)

Here is the summary with links:
  - [f2fs-dev,v3] f2fs: get rid of buffer_head use
    https://git.kernel.org/jaegeuk/f2fs/c/8ce36b8b1150

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: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	willy@infradead.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: get rid of buffer_head use
Date: Mon, 05 Aug 2024 23:30:52 +0000	[thread overview]
Message-ID: <172290065219.2803.34268911020752099.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240618072620.720535-1-chao@kernel.org>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Tue, 18 Jun 2024 15:26:20 +0800 you wrote:
> Convert to use folio and related functionality.
> 
> Cc: Matthew Wilcox <willy@infradead.org>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> - support large folio
> - use bd_mapping instead of bd_inode->i_mapping
>  fs/f2fs/data.c  |  1 -
>  fs/f2fs/f2fs.h  | 11 +++++-
>  fs/f2fs/file.c  |  1 -
>  fs/f2fs/inode.c |  1 -
>  fs/f2fs/super.c | 93 +++++++++++++++++++++++++++++--------------------
>  5 files changed, 66 insertions(+), 41 deletions(-)

Here is the summary with links:
  - [f2fs-dev,v3] f2fs: get rid of buffer_head use
    https://git.kernel.org/jaegeuk/f2fs/c/8ce36b8b1150

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2024-08-05 23:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18  7:26 [f2fs-dev] [PATCH v3] f2fs: get rid of buffer_head use Chao Yu
2024-06-18  7:26 ` Chao Yu
2024-08-05 23:30 ` patchwork-bot+f2fs [this message]
2024-08-05 23:30   ` [f2fs-dev] " 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=172290065219.2803.34268911020752099.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.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.