From: pr-tracker-bot@kernel.org
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [GIT PULL] f2fs for 5.18
Date: Tue, 22 Mar 2022 18:32:03 +0000 [thread overview]
Message-ID: <164797392362.17704.11716595490664039978.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <YjjihIZuvZpUjaSs@google.com>
The pull request you sent on Mon, 21 Mar 2022 13:39:32 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-5.18
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ef510682af3dbe2f9cdae7126a1461c94e010967
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2022-03-22 18:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 20:39 [f2fs-dev] [GIT PULL] f2fs for 5.18 Jaegeuk Kim
2022-03-22 17:22 ` Linus Torvalds
2022-03-22 17:37 ` Waiman Long
2022-03-22 17:50 ` Linus Torvalds
2022-03-22 20:58 ` Jaegeuk Kim
2022-06-15 20:13 ` Pavel Machek
2022-06-16 17:02 ` Jaegeuk Kim
2022-03-23 0:34 ` Tim Murray via Linux-f2fs-devel
2022-03-23 2:03 ` Linus Torvalds
2022-03-23 16:26 ` Jaegeuk Kim
2022-03-23 17:06 ` Linus Torvalds
2022-03-23 21:21 ` Jaegeuk Kim
2022-03-23 7:33 ` Christoph Hellwig
2022-03-23 16:48 ` Jaegeuk Kim
2022-03-23 16:49 ` Christoph Hellwig
2022-03-23 17:00 ` Jaegeuk Kim
2022-03-23 19:28 ` Waiman Long
2022-03-23 21:25 ` Jaegeuk Kim
2022-03-22 18:32 ` pr-tracker-bot [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=164797392362.17704.11716595490664039978.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@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;
as well as URLs for NNTP newsgroup(s).