From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] travis: Add centos7 build
Date: Tue, 25 Aug 2020 08:47:06 +0200 [thread overview]
Message-ID: <20200825064706.GA7135@x230> (raw)
In-Reply-To: <4b7cb95c-fb39-6826-b229-723a1e8bb128@cn.fujitsu.com>
Hi Xu,
> > > I have this idea when I meet ALG_SET_AEAD_ASSOCLEN undefined error on centos7.
> > > Add centos7 travis target, it is more friendly for centos7 user and it is more
> > > meaningful than centos6.
> > OK, how about replacing CentOS 6 with CentOS 7?
> I have no objection about this because my kernel test team only uses
> centos7/8 to test and doesn't use centos6 for a long time.
OK. I don't have either, although I hesitated to sent this patch.
> But I think ltp community should reach a consensus that minimal
> glibc/kernel/gcc(clang) version , so we can drop the corresponding code in
> travis or m4.
> Also, we can raise "Define minimal supported kernel and (g)libc version"
> topic again.
Well, last time I remember we decide to drop CentOS 6 after the release. But I
haven't done it. I also planned to create wiki pagge "Supported kernel and
libc", but haven't done it. Feel free to send a patch for any of these two.
But I'd prefer to do the replacement (7 instead of 6) instead of adding it,
because travis already run for quite long.
Kind regards,
Petr
next prev parent reply other threads:[~2020-08-25 6:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 6:36 [LTP] [PATCH] travis: Add centos7 build Yang Xu
2020-08-24 15:12 ` Petr Vorel
2020-08-25 1:30 ` Yang Xu
2020-08-25 6:47 ` Petr Vorel [this message]
2020-08-25 6:57 ` Yang Xu
2020-08-25 7:14 ` [LTP] [PATCH v2] travis: Use centos:7 instead of centos:6 Yang Xu
2020-08-25 7:17 ` Li Wang
2020-08-28 3:22 ` Yang Xu
2020-08-28 6:40 ` Li Wang
2020-08-28 6:43 ` Li Wang
2020-08-28 7:17 ` Petr Vorel
2020-08-28 10:55 ` Cyril Hrubis
2020-08-28 12:53 ` Petr Vorel
2020-08-28 7:18 ` 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=20200825064706.GA7135@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox