From: Martin Doucha <mdoucha@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 4/5] readahead02: Add max_runtime
Date: Thu, 15 Sep 2022 16:08:58 +0200 [thread overview]
Message-ID: <4bfb03f3-d508-84c4-d7dd-d10234bc0e98@suse.cz> (raw)
In-Reply-To: <YyMuR7825dIOUC6R@yuki>
On 15. 09. 22 15:53, Cyril Hrubis wrote:
> Hi!
> Pushed, thanks.
>
> I guess that for the rest of the problems we should open an issue so
> that we do not forget. Or do you plan to continue working on the test
> after the release?
I'm planning to go back to ULP and KVM tests after release so feel free
to open a new ticket for the other suggested improvements.
--
Martin Doucha mdoucha@suse.cz
QA Engineer for Software Maintenance
SUSE LINUX, s.r.o.
CORSO IIa
Krizikova 148/34
186 00 Prague 8
Czech Republic
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-09-15 14:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 16:19 [LTP] [PATCH v2 0/5] Max_runtime timeout fixes Martin Doucha
2022-09-14 16:19 ` [LTP] [PATCH v2 1/5] ioctl_sg01: Add max_runtime Martin Doucha
2022-09-14 20:27 ` Petr Vorel
2022-09-15 11:51 ` Cyril Hrubis
2022-09-14 16:19 ` [LTP] [PATCH v2 2/5] copy_file_range01: " Martin Doucha
2022-09-14 20:30 ` Petr Vorel
2022-09-14 16:19 ` [LTP] [PATCH v2 3/5] perf_event_open02: " Martin Doucha
2022-09-14 20:31 ` Petr Vorel
2022-09-15 13:43 ` Cyril Hrubis
2022-09-14 16:19 ` [LTP] [PATCH v2 4/5] readahead02: " Martin Doucha
2022-09-14 20:33 ` Petr Vorel
2022-09-15 13:53 ` Cyril Hrubis
2022-09-15 14:08 ` Martin Doucha [this message]
2022-09-16 8:47 ` Cyril Hrubis
2022-09-14 16:19 ` [LTP] [PATCH v2 5/5] sendfile09: " Martin Doucha
2022-09-14 20:34 ` Petr Vorel
2022-09-15 14:06 ` Cyril Hrubis
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=4bfb03f3-d508-84c4-d7dd-d10234bc0e98@suse.cz \
--to=mdoucha@suse.cz \
--cc=chrubis@suse.cz \
--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.