public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] LTP release status
Date: Fri, 13 Jan 2017 14:08:36 +0300	[thread overview]
Message-ID: <5878B534.5020200@oracle.com> (raw)
In-Reply-To: <20170112142828.GC1208@rei.lan>

Hi Cyril,
On 12.01.2017 17:28, Cyril Hrubis wrote:
> Hi!
> I'm done with pre-release testing. The last thing I would like to
> include are fixes for running 32bit LTP on 64bit kernel, particulary
> [PATCH 1/4] lib: Add tst_kernel_bits() patchset and possibly fix the
> issue https://github.com/linux-test-project/ltp/issues/124.
>
> Anything else?
>
> I would like to finally do the release at the start of the next week, is
> that OK with everyone or do we need some more time for pre-release
> testruns?

OK for me. There are NFS test group issues with netns setup, the same as 
found by Petr with telnet test. Don't have working solution right now,  
defer to the next release.

Thanks,
Alexey


  parent reply	other threads:[~2017-01-13 11:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 14:28 [LTP] LTP release status Cyril Hrubis
2017-01-12 14:58 ` Jan Stancek
2017-01-12 15:39   ` Cyril Hrubis
2017-01-16 12:51     ` Jan Stancek
2017-01-16 13:02       ` Cyril Hrubis
2017-01-16 13:19         ` Jan Stancek
2017-01-16 13:30           ` Cyril Hrubis
2017-01-16 14:09             ` Jan Stancek
2017-01-16 14:13               ` Cyril Hrubis
2017-01-16 14:45                 ` Jan Stancek
2017-01-16 14:46                   ` Cyril Hrubis
2017-01-16 15:25               ` Eryu Guan
2017-01-16 15:31                 ` Cyril Hrubis
2017-01-16 15:46                   ` Eryu Guan
2017-01-16 15:40                 ` Jan Stancek
2017-01-13 11:08 ` Alexey Kodanev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-14 18:46 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=5878B534.5020200@oracle.com \
    --to=alexey.kodanev@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox