From: brookxu <brookxu.cn@gmail.com>
To: Balbir Singh <bsingharora@gmail.com>
Cc: adobriyan@gmail.com, akpm@linux-foundation.org,
ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 1/2] delayacct: refactor the code to simplify the implementation
Date: Mon, 19 Apr 2021 17:30:52 +0800 [thread overview]
Message-ID: <eaa0dcbd-999a-eba0-0553-781ffd6be401@gmail.com> (raw)
In-Reply-To: <20210419070106.GC8178@balbir-desktop>
Balbir Singh wrote on 2021/4/19 15:01:
> On Tue, Apr 13, 2021 at 09:37:26AM +0800, brookxu wrote:
>> From: Chunguang Xu <brookxu@tencent.com>
>>
>> The existing data structure is not very convenient for
>> expansion, and part of the code can be saved. Here, try
>> to optimize, which can make the code more concise and
>> easy to expand.
>>
>> Signed-off-by: Chunguang Xu <brookxu@tencent.com>
>
> The approach seems to make sense, but the test robot has found
> a few issues, can you correct those as applicable please?
OK, i will fix it later, thanks for your reply.
> Balbir Singh.
>
prev parent reply other threads:[~2021-04-19 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 1:37 [RESEND PATCH 1/2] delayacct: refactor the code to simplify the implementation brookxu
2021-04-13 1:37 ` [RESEND PATCH 2/2] delayacct: Add a proc file to dump the delay info brookxu
2021-04-13 6:14 ` kernel test robot
2021-04-13 6:14 ` [RFC PATCH] delayacct: delayacct_stats[] can be static kernel test robot
2021-04-13 21:26 ` [RESEND PATCH 2/2] delayacct: Add a proc file to dump the delay info kernel test robot
2021-04-13 23:19 ` [RESEND PATCH 1/2] delayacct: refactor the code to simplify the implementation kernel test robot
2021-04-14 1:24 ` kernel test robot
2021-04-19 7:01 ` Balbir Singh
2021-04-19 9:30 ` brookxu [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=eaa0dcbd-999a-eba0-0553-781ffd6be401@gmail.com \
--to=brookxu.cn@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=ebiederm@xmission.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox