From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] LTP release and code freeze
Date: Tue, 19 Sep 2017 10:48:49 +0200 [thread overview]
Message-ID: <20170919084849.GA14328@rei> (raw)
Hi!
We are getting closer to a release, here is the status as I see it.
Blockers:
* thp01 failing on newer kernels
- I'm waiting for v4 from Ritchie
* utimensat01 failing on stable kernels
- That thread on ML is kind of stuck,
I guess that we will have to accept
both errors for some range of kernels
Nice to have:
* The clone09 patch to disable it on old kernels looks sane to me
- I will merge that one
* CVE synchronization library
- depends if Ritchie can fix it fast enough
* The .needs_rofs patchset looks good to me as well I guess that
it's safe enough to be included in the release as well
Is there anything else I've missing?
--
Cyril Hrubis
chrubis@suse.cz
next reply other threads:[~2017-09-19 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 8:48 Cyril Hrubis [this message]
2017-09-19 18:26 ` [LTP] LTP release and code freeze Sandeep Patil
2017-09-27 13:17 ` Cyril Hrubis
-- strict thread matches above, loose matches on Subject: below --
2017-09-18 7:21 Naresh Kamboju
2017-09-19 8:04 ` Cyril Hrubis
2017-09-25 20:00 ` Naresh Kamboju
2017-09-26 8:51 ` Li Wang
2017-09-26 19:18 ` Naresh Kamboju
2017-09-27 1:52 ` 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=20170919084849.GA14328@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.