From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: Wanlong Gao <gaowanlong@cn.fujitsu.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v1 1/4] lib/tst_kvercmp: Remove old distnames
Date: Tue, 13 Dec 2022 10:40:47 +0100 [thread overview]
Message-ID: <Y5hIn5r39G5gnZWt@pevik> (raw)
In-Reply-To: <CAASaF6wpj3YcJ1gX4g6n7koXL0WnX=9td5RqSjNumrCB+ncmhw@mail.gmail.com>
> On Tue, Dec 13, 2022 at 3:31 AM xuyang2018.jy@fujitsu.com
> <xuyang2018.jy@fujitsu.com> wrote:
> > Hi Jan, Petr
> > > On Mon, Dec 12, 2022 at 4:30 PM Petr Vorel <pvorel@suse.cz> wrote:
> > >> Hi,
> > >>> Our travis-ci has dropped or never used them, they are useless.
> > >>> So delete.
> > >> They were here before CI. They were meant for using by tests
> > >> (no CI related at all).
> > > Right, it's not just CI. RHEL5 is EOL, presumably Oracle as well, so
> > > those likely won't be missed.
> > > RHEL6 has 2 more years - Isn't this removal going to break tst_kvercmp2()?
> > I have removed tst_kvercmp2 usage for RHEL6 in
> > testcases/kernel/syscalls/inotify/inotify04.c and
> > ../kernel/tracing/dynamic_debug/dynamic_debug01.sh, so it should not
> > break tst_kvercmp2.
> OK, you convinced me it's OK to drop it.
> > Also, the current lastest ltp can't ensure that can be compile
> > successfully on rhel6 because of lack of ci, so I think we don't need to
> > still maintain the old version check. If people want to use old kernel
> > ie RHEL6, why not use the old ltp release?
> They can, but they also likely want fixes to tests. I know there have been
> some workarounds, such as using pre-configured LTP to workaround
> autotools issue.
BTW if anybody wishes (and have time) to run some sort of stable branch in LTP
tree, why not? Not sure how many people would be interested to be worth for that
person to invest time.
Kind regards,
Petr
> > ps: @Jan, if you want to keep RHEL6, I will keep it. But two more years,
> > we still need to drop it.
> You showed this isn't significant change for those few users that still might
> exist (and EOL is coming), so:
> Acked-by: Jan Stancek <jstancek@redhat.com>
Thanks Jan for review (suppose ack is just for this first patch).
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-12-13 9:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 11:40 [LTP] [PATCH v1 1/4] lib/tst_kvercmp: Remove old distnames Yang Xu
2022-12-12 11:40 ` [LTP] [PATCH v1 2/4] shell: Remove old kernel version check Yang Xu
2022-12-12 15:34 ` Petr Vorel
2022-12-13 3:08 ` xuyang2018.jy
2022-12-12 11:40 ` [LTP] [PATCH v1 3/4] Remove old kernel version check in C case when using tst_kvercmp Yang Xu
2022-12-12 15:38 ` Petr Vorel
2022-12-13 3:31 ` xuyang2018.jy
2022-12-12 11:40 ` [LTP] [PATCH v1 4/4] Remove old kernel version check when using min_kver Yang Xu
2022-12-12 15:30 ` [LTP] [PATCH v1 1/4] lib/tst_kvercmp: Remove old distnames Petr Vorel
2022-12-12 16:39 ` Jan Stancek
2022-12-13 2:31 ` xuyang2018.jy
2022-12-13 8:55 ` Jan Stancek
2022-12-13 9:40 ` Petr Vorel [this message]
2022-12-13 7:21 ` xuyang2018.jy
2022-12-13 2:34 ` xuyang2018.jy
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=Y5hIn5r39G5gnZWt@pevik \
--to=pvorel@suse.cz \
--cc=gaowanlong@cn.fujitsu.com \
--cc=jstancek@redhat.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