From: patchwork-bot+f2fs@kernel.org
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [GIT PULL] f2fs update for 6.14-rc1
Date: Wed, 29 Jan 2025 00:56:11 +0000 [thread overview]
Message-ID: <173811217199.3973351.14941578865039072034.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Z5hYrgYwNJuaPFF1@google.com>
Hello:
This pull request was applied to jaegeuk/f2fs.git (dev)
by Linus Torvalds <torvalds@linux-foundation.org>:
On Tue, 28 Jan 2025 04:10:22 +0000 you wrote:
> Hi Linus,
>
> Could you please consider this pull request?
>
> Thanks,
>
> The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
>
> [...]
Here is the summary with links:
- [f2fs-dev,GIT,PULL] f2fs update for 6.14-rc1
https://git.kernel.org/jaegeuk/f2fs/c/6d61a53dd6f5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-01-29 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 4:10 [GIT PULL] f2fs update for 6.14-rc1 Jaegeuk Kim
2025-01-28 5:03 ` [f2fs-dev] " pr-tracker-bot
2025-01-29 0:56 ` patchwork-bot+f2fs [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=173811217199.3973351.14941578865039072034.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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