From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH V3] lib: multiply the max_runtime if detect slow kconfigs
Date: Thu, 19 Dec 2024 14:28:00 +0100 [thread overview]
Message-ID: <20241219132800.GC111004@pevik> (raw)
In-Reply-To: <CAEemH2d_P7y+y+P91Lxxi8jBVN1mEjWtt4fh6CRQ07+Bv0yp9Q@mail.gmail.com>
Hi Li, all,
> On Thu, Dec 19, 2024 at 9:07 PM Petr Vorel <pvorel@suse.cz> wrote:
> > +1. Li, could you please do it?
> Sure, but I am wondering do you running the latest LTP branch in productive
> env?
We mostly run LTP stable branch with some exceptions: openSUSE Tumbleweed and
few products in development. Usually it would be more work to backport fixes
to stable package than running master. But sometimes we get a punishment for
this approach :).
> If so I am sorry to make the test time prolong.
> Or if not, could you give me a period to resolve it in a new patch?
Sure.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-12-19 13:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 6:04 [LTP] [PATCH V3] lib: multiply the max_runtime if detect slow kconfigs Li Wang
2024-12-13 22:40 ` Petr Vorel
2024-12-16 9:37 ` Li Wang
2024-12-16 12:28 ` Petr Vorel
2024-12-17 2:40 ` Li Wang
2024-12-16 13:00 ` Cyril Hrubis
2024-12-16 17:29 ` Petr Vorel
2024-12-17 3:46 ` Li Wang
2024-12-18 3:23 ` Li Wang
2024-12-16 12:51 ` Cyril Hrubis
2024-12-19 12:53 ` Petr Vorel
2024-12-19 13:07 ` Li Wang
2024-12-19 12:57 ` Martin Doucha
2024-12-19 13:07 ` Petr Vorel
2024-12-19 13:12 ` Li Wang
2024-12-19 13:28 ` Petr Vorel [this message]
2024-12-19 13:29 ` Cyril Hrubis
2024-12-20 3:59 ` Li Wang
2024-12-20 7:19 ` Li Wang
2024-12-19 13:10 ` Cyril Hrubis
2024-12-19 13:14 ` Li Wang
2024-12-19 13:19 ` Cyril Hrubis
2024-12-19 13:22 ` Li Wang
2024-12-19 13:25 ` 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=20241219132800.GC111004@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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.