From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, thomas@monjalon.net, gakhil@marvell.com
Cc: maxime.coquelin@redhat.com, hernan.vargas@intel.com,
Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v2 1/2] doc: make the Linux drivers doc more generic
Date: Tue, 15 Nov 2022 11:59:13 -0800 [thread overview]
Message-ID: <20221115195914.34700-2-nicolas.chautru@intel.com> (raw)
In-Reply-To: <20221115195914.34700-1-nicolas.chautru@intel.com>
Minor change so that for the documentation to be less NIC centric,
as these steps can apply more generally to PCIe devices.
Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
---
doc/guides/linux_gsg/linux_drivers.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/guides/linux_gsg/linux_drivers.rst b/doc/guides/linux_gsg/linux_drivers.rst
index 2f3f079aab..4f6524ef67 100644
--- a/doc/guides/linux_gsg/linux_drivers.rst
+++ b/doc/guides/linux_gsg/linux_drivers.rst
@@ -12,12 +12,12 @@ Linux Drivers
Different PMDs may require different kernel drivers in order to work properly.
Depending on the PMD being used, a corresponding kernel driver should be loaded,
-and network ports should be bound to that driver.
+and network ports or other hardware devices should be bound to that driver.
.. _linux_gsg_binding_kernel:
-Binding and Unbinding Network Ports to/from the Kernel Modules
---------------------------------------------------------------
+Binding and Unbinding to/from the Kernel Modules
+------------------------------------------------
.. note::
--
2.37.1
next prev parent reply other threads:[~2022-11-15 20:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 19:59 [PATCH v2 0/2] doc: simplify PMD steps Nicolas Chautru
2022-11-15 19:59 ` Nicolas Chautru [this message]
2022-11-22 14:59 ` [PATCH v2 1/2] doc: make the Linux drivers doc more generic Thomas Monjalon
2023-03-06 17:41 ` Chautru, Nicolas
2023-03-06 19:46 ` Thomas Monjalon
2023-03-09 17:35 ` Chautru, Nicolas
2023-03-09 18:08 ` Thomas Monjalon
2022-11-15 19:59 ` [PATCH v2 2/2] doc: simplify the binding steps Nicolas Chautru
2022-11-22 15:01 ` Thomas Monjalon
2022-11-22 21:21 ` Chautru, Nicolas
2022-11-23 8:35 ` Thomas Monjalon
2022-11-24 1:09 ` Chautru, Nicolas
2022-11-24 8:21 ` Thomas Monjalon
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=20221115195914.34700-2-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hernan.vargas@intel.com \
--cc=maxime.coquelin@redhat.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).