From: Bruce Richardson <bruce.richardson@intel.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org, david.marchand@redhat.com, ktraynor@redhat.com,
maxime.coquelin@redhat.com, rasland@nvidia.com,
ajit.khaparde@broadcom.com, honnappa.nagarahalli@arm.com,
aconole@redhat.com, ferruh.yigit@intel.com, mdr@ashroe.eu
Subject: Re: [dpdk-dev] RHEL 7 support
Date: Mon, 11 Apr 2022 10:09:13 +0100 [thread overview]
Message-ID: <YlPwOXuBuUIPnw33@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20220411082313.GB19395@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Mon, Apr 11, 2022 at 01:23:13AM -0700, Tyler Retzlaff wrote:
> On Fri, Jul 09, 2021 at 08:33:28PM +0200, Thomas Monjalon wrote:
> > Hi,
> >
> > I would like to open a discussion about RHEL 7 support in DPDK.
> > How long do we want to support it in new DPDK versions?
> > Can we drop RHEL 7 support starting DPDK 21.11?
>
> did this thread/question ever reach conclusion?
>
I asked around a bit and was informed that there are quite a few users who
are still using CentOS 7, and still need new DPDK to work on that. The fact
of CentOS 8 being EOL'ed at the end of 2021 has probably kept quite a few
users on v7 for now.
/Bruce
prev parent reply other threads:[~2022-04-11 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 18:33 Thomas Monjalon
2021-07-12 17:34 ` Honnappa Nagarahalli
2021-07-13 9:47 ` Kevin Traynor
2021-07-13 15:49 ` Lance Richardson
2021-07-13 16:15 ` Ajit Khaparde
2021-07-19 16:52 ` Tyler Retzlaff
2022-04-11 8:23 ` Tyler Retzlaff
2022-04-11 9:09 ` Bruce Richardson [this message]
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=YlPwOXuBuUIPnw33@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aconole@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mdr@ashroe.eu \
--cc=rasland@nvidia.com \
--cc=roretzla@linux.microsoft.com \
--cc=thomas@monjalon.net \
/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).