From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Swarna Prabhu <sw.prabhu6@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, mcgrof@kernel.org,
s.prabhu@samsung.com, jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: Fix the typos in comments
Date: Wed, 09 Jul 2025 18:10:16 +0000 [thread overview]
Message-ID: <175208461625.806926.1915540263699572760.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250617174047.1511951-1-s.prabhu@samsung.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 17 Jun 2025 17:40:47 +0000 you wrote:
> This patch fixes minor typos in comments in f2fs.
>
> Signed-off-by: Swarna Prabhu <s.prabhu@samsung.com>
> ---
> fs/f2fs/f2fs.h | 6 +++---
> fs/f2fs/node.h | 2 +-
> fs/f2fs/super.c | 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
Here is the summary with links:
- [f2fs-dev] f2fs: Fix the typos in comments
https://git.kernel.org/jaegeuk/f2fs/c/1f136890263c
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
prev parent reply other threads:[~2025-07-09 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 17:40 [f2fs-dev] [PATCH] f2fs: Fix the typos in comments Swarna Prabhu
2025-06-17 18:09 ` Luis Chamberlain via Linux-f2fs-devel
2025-06-24 13:59 ` Chao Yu via Linux-f2fs-devel
2025-07-09 18:10 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=175208461625.806926.1915540263699572760.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=s.prabhu@samsung.com \
--cc=sw.prabhu6@gmail.com \
/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).