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.4
Date: Wed, 26 Apr 2023 23:07:20 +0000 [thread overview]
Message-ID: <168255044066.16014.6020850362177131584.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZEgdmJWhJX9NJ0fG@google.com>
Hello:
This pull request was applied to jaegeuk/f2fs.git (dev)
by Linus Torvalds <torvalds@linux-foundation.org>:
On Tue, 25 Apr 2023 11:36:08 -0700 you wrote:
> Hi Linus,
>
> Could you please consider this pull request?
>
> Thanks,
>
> The following changes since commit ffe78bbd512166e0ef1cc4858010b128c510ed7d:
>
> [...]
Here is the summary with links:
- [f2fs-dev,GIT,PULL] f2fs update for 6.4
https://git.kernel.org/jaegeuk/f2fs/c/5c7ecada25d2
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 6.4
Date: Wed, 26 Apr 2023 23:07:20 +0000 [thread overview]
Message-ID: <168255044066.16014.6020850362177131584.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZEgdmJWhJX9NJ0fG@google.com>
Hello:
This pull request was applied to jaegeuk/f2fs.git (dev)
by Linus Torvalds <torvalds@linux-foundation.org>:
On Tue, 25 Apr 2023 11:36:08 -0700 you wrote:
> Hi Linus,
>
> Could you please consider this pull request?
>
> Thanks,
>
> The following changes since commit ffe78bbd512166e0ef1cc4858010b128c510ed7d:
>
> [...]
Here is the summary with links:
- [f2fs-dev,GIT,PULL] f2fs update for 6.4
https://git.kernel.org/jaegeuk/f2fs/c/5c7ecada25d2
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:[~2023-04-26 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 18:36 [f2fs-dev] [GIT PULL] f2fs update for 6.4 Jaegeuk Kim
2023-04-25 18:36 ` Jaegeuk Kim
2023-04-26 17:06 ` [f2fs-dev] " pr-tracker-bot
2023-04-26 17:06 ` pr-tracker-bot
2023-04-26 23:07 ` patchwork-bot+f2fs [this message]
2023-04-26 23:07 ` [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=168255044066.16014.6020850362177131584.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 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.