From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: add support for counting time of submit discard cmd
Date: Wed, 14 Dec 2022 13:52:26 -0800 [thread overview]
Message-ID: <Y5pFmv4AUDxw9GI9@google.com> (raw)
In-Reply-To: <20221214072830.32911-1-frank.li@vivo.com>
On 12/14, Yangtao Li wrote:
> Hi Jaegeuk,
>
> > I cut off the patches for this merge window. Please consider next release.
>
> Alright, thanks for your reminder.
>
> > BTW, could you please send a patch set instead of random posts?
>
> Most of the patches were noticed when I looked at the code, and they were scattered.
> On the one hand, there is not much relationship between them, so I send patches based
> on the f2fs-dev branch every time. On the other hand, it is also to avoid that a patch
> may not be received and block subsequent patches.
>
> > It's quite hard to find which one was merged or not.
>
> Why not to use patchwork to manage patches?
> This tool is used by many kernel subsystems. And This tool has a more friendly
> interface and can mark the status of the patch.
>
> https://korg.wiki.kernel.org/userdoc/patchwork#adding_patchwork-bot_integration
Good idea. I requested to add f2fs project there. :) Let's see.
>
> Thx,
> Yangtao
_______________________________________________
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: Jaegeuk Kim <jaegeuk@kernel.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] f2fs: add support for counting time of submit discard cmd
Date: Wed, 14 Dec 2022 13:52:26 -0800 [thread overview]
Message-ID: <Y5pFmv4AUDxw9GI9@google.com> (raw)
In-Reply-To: <20221214072830.32911-1-frank.li@vivo.com>
On 12/14, Yangtao Li wrote:
> Hi Jaegeuk,
>
> > I cut off the patches for this merge window. Please consider next release.
>
> Alright, thanks for your reminder.
>
> > BTW, could you please send a patch set instead of random posts?
>
> Most of the patches were noticed when I looked at the code, and they were scattered.
> On the one hand, there is not much relationship between them, so I send patches based
> on the f2fs-dev branch every time. On the other hand, it is also to avoid that a patch
> may not be received and block subsequent patches.
>
> > It's quite hard to find which one was merged or not.
>
> Why not to use patchwork to manage patches?
> This tool is used by many kernel subsystems. And This tool has a more friendly
> interface and can mark the status of the patch.
>
> https://korg.wiki.kernel.org/userdoc/patchwork#adding_patchwork-bot_integration
Good idea. I requested to add f2fs project there. :) Let's see.
>
> Thx,
> Yangtao
next prev parent reply other threads:[~2022-12-14 21:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 12:51 [f2fs-dev] [PATCH v2] f2fs: add support for counting time of submit discard cmd Yangtao Li via Linux-f2fs-devel
2022-12-12 12:51 ` Yangtao Li
2022-12-12 13:40 ` [f2fs-dev] " Chao Yu
2022-12-12 13:40 ` Chao Yu
2022-12-12 22:47 ` [f2fs-dev] " Jaegeuk Kim
2022-12-12 22:47 ` Jaegeuk Kim
2022-12-13 1:22 ` [f2fs-dev] " Chao Yu
2022-12-13 1:22 ` Chao Yu
2022-12-13 12:21 ` [f2fs-dev] " Yangtao Li via Linux-f2fs-devel
2022-12-13 12:21 ` Yangtao Li
2022-12-13 19:17 ` [f2fs-dev] " Jaegeuk Kim
2022-12-13 19:17 ` Jaegeuk Kim
2022-12-14 7:28 ` [f2fs-dev] " Yangtao Li via Linux-f2fs-devel
2022-12-14 7:28 ` Yangtao Li
2022-12-14 21:52 ` Jaegeuk Kim [this message]
2022-12-14 21:52 ` Jaegeuk Kim
2022-12-16 1:04 ` [f2fs-dev] " Chao Yu
2022-12-16 1:04 ` Chao Yu
2022-12-16 2:49 ` [f2fs-dev] " Yangtao Li via Linux-f2fs-devel
2022-12-16 2:49 ` Yangtao Li
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=Y5pFmv4AUDxw9GI9@google.com \
--to=jaegeuk@kernel.org \
--cc=frank.li@vivo.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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.