From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/inotify06: bump timeout
Date: Fri, 13 Apr 2018 17:41:43 +0200 [thread overview]
Message-ID: <20180413154143.GB25041@rei> (raw)
In-Reply-To: <96166bd70a154ff7a440a8fabb8cb3395d6f5ce3.1523629313.git.jstancek@redhat.com>
Hi!
> After migrating this test to newlib, there's now
> a default timeout and it's not enough for some
> systems.
I would consider that obvious enough to go directly to the git,
acked nevertheless.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-04-13 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 14:22 [LTP] [PATCH] syscalls/inotify06: bump timeout Jan Stancek
2018-04-13 15:41 ` Cyril Hrubis [this message]
2018-04-13 15:45 ` Jan Stancek
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=20180413154143.GB25041@rei \
--to=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.