DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Young <dave@youngcopy.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
	Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH v2] docs: freebsd: Update to 20.11
Date: Mon, 03 Jul 2023 17:19:18 +0200	[thread overview]
Message-ID: <9128157.CDJkKcVGEf@thomas> (raw)
In-Reply-To: <20230630164146.1378-1-dave@youngcopy.com>

30/06/2023 18:41, David Young:
> This patch updates the installation instructions for DPDK on FreeBSD.
> It specifies the explicit version of DPDK (20.11) to be installed.
> This change is important as the 'dpdk' package is an alias and doesn't
> always point to the latest version. By specifying the explicit version,
> we make it clear which version is to be installed. The page previously
> showed 'pkg install dpdk' without specifying the version.

I understand it can be helpful to choose a specific version.
But dpdk20.11 is not necessarily the latest one,
and it could be useful to show both approaches in the doc.

> @@ -123,3 +123,4 @@ via the contigmem module, and 4 NIC ports bound to the nic_uio module::
>  
>     For an explanation of the command-line parameters that can be passed to an
>     DPDK application, see section :ref:`running_sample_app`.
> +

This last line looks like an extra unnneeded blank line.




  reply	other threads:[~2023-07-03 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 18:12 [PATCH] Updated to dpdk20.11 David Young
2023-06-29 18:26 ` Aaron Conole
2023-06-30 16:41 ` [PATCH v2] docs: freebsd: Update to 20.11 David Young
2023-07-03 15:19   ` Thomas Monjalon [this message]
2023-07-17 13:35     ` Bruce Richardson
2023-07-06 20:36 ` [PATCH v3] " David Young
2024-10-04 16:01   ` 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=9128157.CDJkKcVGEf@thomas \
    --to=thomas@monjalon.net \
    --cc=aconole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dave@youngcopy.com \
    --cc=dev@dpdk.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).