From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
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 7.2-rc1
Date: Wed, 24 Jun 2026 08:59:34 +0000 [thread overview]
Message-ID: <178229157429.2577930.9752405343308255841.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ajrLmn16uMPcc4Lv@google.com>
Hello:
This pull request was applied to jaegeuk/f2fs.git (dev)
by Linus Torvalds <torvalds@linux-foundation.org>:
On Tue, 23 Jun 2026 18:08:26 +0000 you wrote:
> Hi Linus,
>
> Could you please consider this pull request? Given that the git history shows
> less than a day since the last update, it is completely fine to let it soak in
> -next for a bit. I submitted this because I needed to remove an old patch that
> was incorrectly merged a while ago, and I wanted to clean up the tree.
>
> [...]
Here is the summary with links:
- [f2fs-dev,GIT,PULL] f2fs update for 7.2-rc1
https://git.kernel.org/jaegeuk/f2fs/c/09ca8dc7d634
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: 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 7.2-rc1
Date: Wed, 24 Jun 2026 08:59:34 +0000 [thread overview]
Message-ID: <178229157429.2577930.9752405343308255841.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ajrLmn16uMPcc4Lv@google.com>
Hello:
This pull request was applied to jaegeuk/f2fs.git (dev)
by Linus Torvalds <torvalds@linux-foundation.org>:
On Tue, 23 Jun 2026 18:08:26 +0000 you wrote:
> Hi Linus,
>
> Could you please consider this pull request? Given that the git history shows
> less than a day since the last update, it is completely fine to let it soak in
> -next for a bit. I submitted this because I needed to remove an old patch that
> was incorrectly merged a while ago, and I wanted to clean up the tree.
>
> [...]
Here is the summary with links:
- [f2fs-dev,GIT,PULL] f2fs update for 7.2-rc1
https://git.kernel.org/jaegeuk/f2fs/c/09ca8dc7d634
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:[~2026-06-24 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 18:08 [f2fs-dev] [GIT PULL] f2fs update for 7.2-rc1 Jaegeuk Kim via Linux-f2fs-devel
2026-06-23 18:08 ` Jaegeuk Kim
2026-06-24 1:51 ` [f2fs-dev] " pr-tracker-bot--- via Linux-f2fs-devel
2026-06-24 1:51 ` pr-tracker-bot
2026-06-24 8:59 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-06-24 8:59 ` [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=178229157429.2577930.9752405343308255841.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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 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.