From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>, Min Zhou <zhoumin@loongson.cn>
Cc: "Morten Brørup" <mb@smartsharesystems.com>,
dev@dpdk.org, "Patrick Robb" <probb@iol.unh.edu>,
"Aaron Conole" <aconole@redhat.com>
Subject: Re: [PATCH] doc: update minimum Linux kernel version
Date: Tue, 30 Jul 2024 16:27:21 -0700 [thread overview]
Message-ID: <20240730162721.0e065a1d@hermes.local> (raw)
In-Reply-To: <2213386.C4sosBPzcN@thomas>
On Mon, 29 Jul 2024 22:07:10 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > This patch is too late for 24.03 release, by the time the next one happens,
> > we can drop CentOS 7 as well as the old kernel.
>
> Applied this kernel minimum bump.
>
> Please send another patch for dropping RHEL/CentOS 7.
I noticed that the cross build instructions for loongarch are referring
to out of date releases and tool chains. Debian 10 and CentOS 8 are both
end of life. Also, it looks like the current GNU compiler supports this
architecture so using a tarball cross build package is no longer needed.
Other parts of the doc's look out of date here for LoongArch as well.
next prev parent reply other threads:[~2024-07-30 23:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 16:57 Stephen Hemminger
2024-01-11 9:18 ` Morten Brørup
2024-01-11 18:48 ` Aaron Conole
2024-01-11 19:02 ` Patrick Robb
2024-01-11 19:26 ` Morten Brørup
2024-01-11 19:50 ` Patrick Robb
2024-01-11 19:54 ` Stephen Hemminger
2024-01-11 22:38 ` Morten Brørup
2024-02-16 3:05 ` Stephen Hemminger
2024-02-16 8:29 ` Morten Brørup
2024-02-16 17:22 ` Stephen Hemminger
2024-02-16 17:42 ` Stephen Hemminger
2024-02-17 19:48 ` Patrick Robb
2024-07-29 20:07 ` Thomas Monjalon
2024-07-30 23:27 ` Stephen Hemminger [this message]
2024-07-30 23:40 ` [PATCH] doc: no longer support end of life CentOS versions Stephen Hemminger
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=20240730162721.0e065a1d@hermes.local \
--to=stephen@networkplumber.org \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=zhoumin@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).