From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/8] syscalls/futex: Add support for time64 tests
Date: Fri, 8 May 2020 08:55:19 +0200 [thread overview]
Message-ID: <20200508065519.GA2556@x230> (raw)
In-Reply-To: <20200508042455.xmf57rcdhtmxqeec@vireshk-i7>
Hi Viresh,
> > Will it be easier if I resend all my patches again in a single series
> > ? I can also add the new tests I have converted then.
> Okay, I cleaned up the GPL licensing thing and resent everything in a
> single series. That should simplify everyone's life.
Thanks a lot!
It might not make it to this release (freeze should be from Monday and probably
nobody from reviewers work on the weekend + there is a bank holiday today for
some countries).
Kind regards,
Petr
next prev parent reply other threads:[~2020-05-08 6:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 9:12 [LTP] [PATCH 1/8] syscalls/futex: Merge futex_wait_bitset tests Viresh Kumar
2020-05-05 9:12 ` [LTP] [PATCH 2/8] syscalls/futex: Add support for time64 tests Viresh Kumar
2020-05-07 14:52 ` Petr Vorel
2020-05-08 3:30 ` Viresh Kumar
2020-05-08 4:24 ` Viresh Kumar
2020-05-08 6:55 ` Petr Vorel [this message]
2020-05-08 7:03 ` Viresh Kumar
2020-05-07 15:19 ` Petr Vorel
2020-05-05 9:12 ` [LTP] [PATCH 3/8] syscalls/io_pgetevents: " Viresh Kumar
2020-05-05 9:12 ` [LTP] [PATCH 4/8] syscalls/sigwaitinfo: Migrate to new test framework Viresh Kumar
2020-05-05 9:12 ` [LTP] [PATCH 5/8] syscalls/rt_sigtimedwait: Add support for time64 tests Viresh Kumar
2020-05-05 9:12 ` [LTP] [PATCH 6/8] syscalls/mq_timed{send|receive}: " Viresh Kumar
2020-05-05 9:12 ` [LTP] [PATCH 7/8] syscalls/recvmmsg: " Viresh Kumar
2020-05-05 9:12 ` [LTP] [PATCH 8/8] syscalls/ppoll: " Viresh Kumar
2020-05-07 14:59 ` [LTP] [PATCH 1/8] syscalls/futex: Merge futex_wait_bitset tests 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=20200508065519.GA2556@x230 \
--to=pvorel@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.