From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] LTP Release plans
Date: Thu, 9 Jan 2020 11:19:09 +0100 [thread overview]
Message-ID: <20200109101909.GD23230@dell5510> (raw)
In-Reply-To: <20200106150329.GC26880@rei.lan>
Hi Cyril,
> Anything else I should look at?
I'd like to have TI-RPC related patch-set
* RFC,1/1] rpc-tirpc: Remove authdes related tests
https://patchwork.ozlabs.org/patch/1216506/
Acked by Li, waiting for Steve (libtirpc maintainer) to be acked.
And if you have time then this one (not that important, fixing
https://github.com/linux-test-project/ltp/pull/628
and adding libntirpc support):
* TI-RPC: enhancements (pkg-config, libntirpc, travis)
https://patchwork.ozlabs.org/project/ltp/list/?series=151849
(first 2 commits are relevant, the others are travis)
Thanks!
Kind regards,
Petr
next prev parent reply other threads:[~2020-01-09 10:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 12:54 [LTP] LTP Release plans Cyril Hrubis
2019-12-13 13:06 ` Martin Doucha
2020-01-06 14:57 ` Cyril Hrubis
2019-12-17 10:26 ` Yang Xu
2020-01-06 14:58 ` Cyril Hrubis
2020-01-06 15:03 ` Cyril Hrubis
2020-01-07 2:03 ` Yang Xu
2020-01-07 3:02 ` Yang Xu
2020-01-08 15:25 ` Cyril Hrubis
2020-01-09 10:19 ` Petr Vorel [this message]
2020-01-15 16:15 ` Cyril Hrubis
2020-01-16 16:15 ` Li Wang
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=20200109101909.GD23230@dell5510 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox