From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: Re: CentOs End of Life?
Date: Tue, 30 Jan 2024 17:33:06 +0000 [thread overview]
Message-ID: <Zbky0kzhqoAKTT8V@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20240130091849.0c2b7b8b@hermes.local>
On Tue, Jan 30, 2024 at 09:18:49AM -0800, Stephen Hemminger wrote:
> While reworking tap device, one issue is how to keep (or drop) the support
> of older Enterprise releases. The tap flow support is doing some workarounds
> to include missing support, but these are not the right way to do it.
>
> The question is: is this even worth keeping?
> CentOS 7 reaches end of life in June 2024.
> CentOS 7 is using a kernel which is no longer supported.
>
> If we drop CentOS 7, that means dropping RHEL7 and would need to be hightlighted
> in the docs.
I thought we had already dropped it. Centos 7 doesn't come by default with
a C11-supporting compiler.
/Bruce
next prev parent reply other threads:[~2024-01-30 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 17:18 CentOs End of Life? Stephen Hemminger
2024-01-30 17:33 ` Bruce Richardson [this message]
2024-01-30 17:45 ` Stephen Hemminger
2024-01-30 19:10 ` Tyler Retzlaff
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=Zbky0kzhqoAKTT8V@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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.