All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: "Patrick Robb" <probb@iol.unh.edu>,
	"Aaron Conole" <aconole@redhat.com>, <dev@dpdk.org>
Subject: Re: [PATCH] doc: update minimum Linux kernel version
Date: Fri, 16 Feb 2024 09:42:52 -0800	[thread overview]
Message-ID: <20240216094252.0d3505fa@hermes.local> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F223@smartserver.smartshare.dk>

On Fri, 16 Feb 2024 09:29:47 +0100
Morten Brørup <mb@smartsharesystems.com> wrote:

> The system requirements in the Getting Started Guide [1] says:
> 
> Kernel version >= 4.14
> The kernel version required is based on the oldest long term stable kernel available at kernel.org when the DPDK version is in development.
> Compatibility for recent distribution kernels will be kept, notably RHEL/CentOS 7.
> 
> [1]: https://doc.dpdk.org/guides/linux_gsg/sys_reqs.html#system-software
> 
> If we consider it API breakage to change that, we have to wait until the 24.11 release.
> For future DPDK LTS releases, we should be more careful about what we claim to support. And again: If we claim to support something, people expect it to be tested in CI.
> 
> Disregarding the API breakage by stopping support for a system we claim to support... RHEL7 testing was changed to LTS only [2], that should probably have been applied to CentOS 7 too.
> 
> [2]: https://inbox.dpdk.org/dev/CAJvnSUBcq3gznQD4k=krQ+gu2OxTxA2YJBc=J=LtidFXqgg_hg@mail.gmail.com/
> 

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.

  parent reply	other threads:[~2024-02-16 17:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 16:57 [PATCH] doc: update minimum Linux kernel version 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 [this message]
2024-02-17 19:48                 ` Patrick Robb
2024-07-29 20:07                 ` Thomas Monjalon
2024-07-30 23:27                   ` Stephen Hemminger
2024-07-30 23:40                   ` [PATCH] doc: no longer support end of life CentOS versions Stephen Hemminger
2024-11-19 15:34                     ` Thomas Monjalon
2024-11-19 18:40                       ` Stephen Hemminger
2024-11-19 19:38                         ` Thomas Monjalon
2024-11-19 23:09                     ` [PATCH v2] " Stephen Hemminger
2025-07-21 12:40                       ` Kevin Traynor
2025-07-21 12:50                       ` David Marchand

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=20240216094252.0d3505fa@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=probb@iol.unh.edu \
    /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.