From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: Li Wang <liwan@redhat.com>, Chunfu Wen <chwen@redhat.com>
Cc: Charles Shi <cheshi@redhat.com>,
ltp@lists.linux.it, Irene Diez <idiez@redhat.com>
Subject: Re: [LTP] [PATCH v4] Add test case to cover the setting resource limit64 for process
Date: Fri, 28 Feb 2025 08:45:25 +0100 [thread overview]
Message-ID: <54cd690b-dd2a-4285-8d53-5aef05be3d6c@suse.com> (raw)
In-Reply-To: <CAEemH2cpdqSViHfDcRfFqsWtz4kkrkhU4DymfXW+5REPEMvYTw@mail.gmail.com>
Hi Li,
thanks for checking, but we still missed a couple of things to fix, like
infinite loop that might cause some issues and it should be replaced
with checkpoints as pointed out by Petr.
Best regards,
Andrea Cervesato
On 2/28/25 04:41, Li Wang wrote:
> On Wed, Feb 26, 2025 at 9:15 AM Chunfu Wen <chwen@redhat.com> wrote:
>
>> Hello Maintainers,
>>
>> Could you please help me review the V4 patch when you have time?
>>
> I helped resolve the code conflict and pushed, thanks!
>
> Li Wang
>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-02-28 7:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 2:31 [LTP] [PATCH] Add test case to cover the setting resource limit64 for process chunfuwen
2025-02-18 11:44 ` Ricardo B. Marlière
2025-02-18 13:29 ` Andrea Cervesato via ltp
2025-02-19 2:35 ` Chunfu Wen
2025-02-19 9:29 ` Andrea Cervesato via ltp
2025-02-19 6:47 ` [LTP] [PATCH v2] " chunfuwen
2025-02-19 16:44 ` Petr Vorel
2025-02-20 2:08 ` Li Wang
2025-02-20 9:35 ` Petr Vorel
2025-02-20 8:01 ` Chunfu Wen
2025-02-20 8:35 ` [LTP] [PATCH v3] " Chunfu Wen
2025-02-21 10:34 ` Andrea Cervesato via ltp
2025-02-24 3:06 ` Chunfu Wen
2025-02-24 3:07 ` [LTP] [PATCH v4] " Chunfu Wen
2025-02-26 1:15 ` Chunfu Wen
2025-02-28 3:41 ` Li Wang
2025-02-28 7:45 ` Andrea Cervesato via ltp [this message]
2025-02-28 8:39 ` Li Wang
2025-02-28 9:22 ` Li Wang
2025-02-28 11:37 ` Petr Vorel
2025-02-26 9:21 ` Li Wang
2025-02-19 16:50 ` [LTP] [PATCH v2] " Petr Vorel
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=54cd690b-dd2a-4285-8d53-5aef05be3d6c@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=cheshi@redhat.com \
--cc=chwen@redhat.com \
--cc=idiez@redhat.com \
--cc=liwan@redhat.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