public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: "Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Jan Lübbe" <jlu@pengutronix.de>, "Khem Raj" <raj.khem@gmail.com>,
	"Richard Palethorpe" <rpalethorpe@suse.com>,
	ltp@lists.linux.it, automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] [RFC PATCH 1/2] doc: State the minimal kernel version
Date: Tue, 20 Dec 2022 12:19:17 +0100	[thread overview]
Message-ID: <Y6GaNcnDTAEGaAh9@pevik> (raw)
In-Reply-To: <CAEemH2d=kNwrAmrvy21Si4wF9H0qqg_Zkq=12S9ZC=11MQKFSw@mail.gmail.com>

> On Mon, Dec 19, 2022 at 5:52 PM Jan Stancek <jstancek@redhat.com> wrote:

> > On Fri, Dec 16, 2022 at 10:46 AM Petr Vorel <pvorel@suse.cz> wrote:

> > > Because the tested version does not automatically mean the minimal
> > > supported.

> > > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > > ---
> > > Hi all,

> > > I'm sorry to bother you, many of you concentrate on current mainline (or
> > > supported stable) instead of digging into history. But you might know
> > > about somebody who still cares about 3.x. Although not many of these
> > > people would try to run recent LTP on these old versions, but we never
> > > know.

> > > I started with 3.0 as that was the result of the old discussions over
> > > ML.  I'm perfectly ok, if we raise it to 3.10, which is tested.
> > > I guess after CentOS 7 EOL we should raise support even higher.

> > I'd be fine with raising it to 3.10, that still covers CentOS7 for now.
> > (3.10 will be 10 years old in couple months)


> +1 that's exactly!

OK, is anybody against raising the support to 3.10?

If not, I can change it:

-Minimal supported (although untested) kernel version is 3.0.
+Minimal supported kernel version is 3.10.

Kind regards,
Petr

> Reviewed-by: Li Wang <liwang@redhat.com>



> > Acked-by: Jan Stancek <jstancek@redhat.com>


> > > The motivation is to state the version here, instead in
> > > doc/c-test-api.txt

> > https://patchwork.ozlabs.org/project/ltp/patch/1671166923-2173-7-git-send-email-xuyang2018.jy@fujitsu.com/

> > > Also stating kernel version limits minimal libc version.
> > > Thus I'm not going to start a discussion about what libc version we
> > > support.

> > > Kind regards,
> > > Petr

> > >  doc/supported-kernel-libc-versions.txt | 7 ++++++-
> > >  1 file changed, 6 insertions(+), 1 deletion(-)

> > > diff --git a/doc/supported-kernel-libc-versions.txt
> > b/doc/supported-kernel-libc-versions.txt
> > > index e48e3aeae3..f89c4882fb 100644
> > > --- a/doc/supported-kernel-libc-versions.txt
> > > +++ b/doc/supported-kernel-libc-versions.txt
> > > @@ -51,7 +51,12 @@ distribution you may as well reconsider you life
> > choices.
> > >  | s390x         | cross compilation
> > >  |==================================

> > > -1.3 Supported libc
> > > +1.3 Minimal supported kernel version
> > > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > +
> > > +Minimal supported (although untested) kernel version is 3.0.
> > > +
> > > +1.4 Supported libc
> > >  ~~~~~~~~~~~~~~~~~~

> > >  [align="center",options="header"]
> > > --
> > > 2.39.0

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-12-20 11:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  9:46 [LTP] [RFC PATCH 0/2] Document minimal supported LTP version Petr Vorel
2022-12-16  9:46 ` [LTP] [RFC PATCH 1/2] doc: State the minimal kernel version Petr Vorel
2022-12-19  9:52   ` Jan Stancek
2022-12-20  4:58     ` Li Wang
2022-12-20 11:19       ` Petr Vorel [this message]
2022-12-20 11:31         ` Richard Purdie
2022-12-19 18:12   ` Khem Raj
2022-12-16  9:46 ` [LTP] [RFC PATCH 2/2] doc: Document used C standard Petr Vorel
2022-12-19  3:04   ` xuyang2018.jy
2022-12-20  5:00   ` Li Wang
2022-12-19 14:41 ` [LTP] [RFC PATCH 0/2] Document minimal supported LTP version Richard Palethorpe

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=Y6GaNcnDTAEGaAh9@pevik \
    --to=pvorel@suse.cz \
    --cc=alexandre.belloni@bootlin.com \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=jlu@pengutronix.de \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=raj.khem@gmail.com \
    --cc=rpalethorpe@suse.com \
    /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