DPDK patches and discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: "Stephen Hemminger" <stephen@networkplumber.org>,  <dev@dpdk.org>,
	Patrick Robb <probb@iol.unh.edu>
Subject: Re: [PATCH] doc: update minimum Linux kernel version
Date: Thu, 11 Jan 2024 13:48:11 -0500	[thread overview]
Message-ID: <f7tjzofd7v8.fsf@redhat.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F124@smartserver.smartshare.dk> ("Morten =?utf-8?Q?Br=C3=B8rup=22's?= message of "Thu, 11 Jan 2024 10:18:34 +0100")

Morten Brørup <mb@smartsharesystems.com> writes:

>> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
>> Sent: Wednesday, 10 January 2024 17.58
>> 
>> The last version of 4.14 kernel was just released (4.14.336),
>> and it is now end of life. Update the DPDK kernel minimum version
>> to the next LTS kernel version.
>> 
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>> ---
>>  doc/guides/linux_gsg/sys_reqs.rst | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> diff --git a/doc/guides/linux_gsg/sys_reqs.rst
>> b/doc/guides/linux_gsg/sys_reqs.rst
>> index 13be715933f4..9c5282573e4a 100644
>> --- a/doc/guides/linux_gsg/sys_reqs.rst
>> +++ b/doc/guides/linux_gsg/sys_reqs.rst
>> @@ -106,7 +106,7 @@ System Software
>> 
>>  **Required:**
>> 
>> -*   Kernel version >= 4.14
>> +*   Kernel version >= 4.19
>> 
>>      The kernel version required is based on the oldest long term
>> stable kernel available
>>      at kernel.org when the DPDK version is in development.
>> --
>> 2.43.0
>
> I wonder if any automated tests are using this specific kernel
> version, or if we are only testing using the distros' native
> kernels. @Aaron?

I believe that we generally try to keep to the distro version.  There
are some exceptions for specific platforms (that is to support specific
pieces of hardware, but those are very recent).

> Regardless, the documented version requirement needs updating, so...
>
> Acked-by: Morten Brørup <mb@smartsharesystems.com>


  reply	other threads:[~2024-01-11 18:48 UTC|newest]

Thread overview: 20+ 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 [this message]
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
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

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=f7tjzofd7v8.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=probb@iol.unh.edu \
    --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 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).