DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/4] Replace references to ifconfig in doc
Date: Tue,  2 Apr 2024 09:29:32 -0700	[thread overview]
Message-ID: <20240402163050.133923-1-stephen@networkplumber.org> (raw)

Replace references to ifconfig in documentation.
The ifconfig command is deprecated and has been replaced by
iproute2 for 20 years.

Stephen Hemminger (4):
  doc: remove references to ifconfig
  doc: replace ifconfig and brctl usage in howto
  doc: replace ifconfig in testpmd doc
  doc: replace use of ifconfig in nics

 doc/guides/howto/lm_bond_virtio_sriov.rst   | 58 ++++++++++-----------
 doc/guides/howto/lm_virtio_vhost_user.rst   |  2 +-
 doc/guides/linux_gsg/linux_drivers.rst      |  2 +-
 doc/guides/nics/bnx2x.rst                   |  4 +-
 doc/guides/nics/cxgbe.rst                   | 13 +++--
 doc/guides/nics/e1000em.rst                 |  2 +-
 doc/guides/nics/i40e.rst                    |  2 +-
 doc/guides/nics/mlx5.rst                    |  2 +-
 doc/guides/nics/qede.rst                    |  4 +-
 doc/guides/testpmd_app_ug/testpmd_funcs.rst |  3 +-
 10 files changed, 46 insertions(+), 46 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-04-02 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 16:29 Stephen Hemminger [this message]
2024-04-02 16:29 ` [PATCH 1/4] doc: remove references to ifconfig Stephen Hemminger
2024-04-02 16:29 ` [PATCH 2/4] doc: replace ifconfig and brctl usage in howto Stephen Hemminger
2024-04-02 16:29 ` [PATCH 3/4] doc: replace ifconfig in testpmd doc Stephen Hemminger
2024-04-02 16:29 ` [PATCH 4/4] doc: replace use of ifconfig in nics Stephen Hemminger
2024-04-02 16:39 ` [PATCH 0/4] Replace references to ifconfig in doc Bruce Richardson

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=20240402163050.133923-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --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).