From: Guangbin Huang <huangguangbin2@huawei.com>
To: <davem@davemloft.net>, <kuba@kernel.org>, <jiri@nvidia.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lipeng321@huawei.com>, <moyufeng@huawei.com>,
<chenhao288@hisilicon.com>, <huangguangbin2@huawei.com>
Subject: [PATCH V3 net-next 1/7] devlink: add documentation for hns3 driver
Date: Mon, 26 Jul 2021 10:47:01 +0800 [thread overview]
Message-ID: <1627267627-38467-2-git-send-email-huangguangbin2@huawei.com> (raw)
In-Reply-To: <1627267627-38467-1-git-send-email-huangguangbin2@huawei.com>
From: Hao Chen <chenhao288@hisilicon.com>
Add a file to document devlink support for hns3 driver, now support devlink
info and devlink reload.
Signed-off-by: Hao Chen <chenhao288@hisilicon.com>
Signed-off-by: Guangbin Huang <huangguangbin2@huawei.com>
---
Documentation/networking/devlink/hns3.rst | 25 +++++++++++++++++++++++++
Documentation/networking/devlink/index.rst | 1 +
2 files changed, 26 insertions(+)
create mode 100644 Documentation/networking/devlink/hns3.rst
diff --git a/Documentation/networking/devlink/hns3.rst b/Documentation/networking/devlink/hns3.rst
new file mode 100644
index 000000000000..4562a6e4782f
--- /dev/null
+++ b/Documentation/networking/devlink/hns3.rst
@@ -0,0 +1,25 @@
+.. SPDX-License-Identifier: GPL-2.0
+
+====================
+hns3 devlink support
+====================
+
+This document describes the devlink features implemented by the ``hns3``
+device driver.
+
+The ``hns3`` driver supports reloading via ``DEVLINK_CMD_RELOAD``.
+
+Info versions
+=============
+
+The ``hns3`` driver reports the following versions
+
+.. list-table:: devlink info versions implemented
+ :widths: 10 10 80
+
+ * - Name
+ - Type
+ - Description
+ * - ``fw``
+ - running
+ - Used to represent the firmware version.
diff --git a/Documentation/networking/devlink/index.rst b/Documentation/networking/devlink/index.rst
index b3b9e0692088..03f56ed2961f 100644
--- a/Documentation/networking/devlink/index.rst
+++ b/Documentation/networking/devlink/index.rst
@@ -34,6 +34,7 @@ parameters, info versions, and other features it supports.
:maxdepth: 1
bnxt
+ hns3
ionic
ice
mlx4
--
2.8.1
next prev parent reply other threads:[~2021-07-26 2:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 2:47 [PATCH V3 net-next 0/7] net: hns3: add support devlink Guangbin Huang
2021-07-26 2:47 ` Guangbin Huang [this message]
2021-07-26 2:47 ` [PATCH V3 net-next 2/7] net: hns3: add support for registering devlink for PF Guangbin Huang
2021-07-26 2:47 ` [PATCH V3 net-next 3/7] net: hns3: add support for registering devlink for VF Guangbin Huang
2021-07-26 2:47 ` [PATCH V3 net-next 4/7] net: hns3: add support for devlink get info for PF Guangbin Huang
2021-07-26 2:47 ` [PATCH V3 net-next 5/7] net: hns3: add support for devlink get info for VF Guangbin Huang
2021-07-26 2:47 ` [PATCH V3 net-next 6/7] net: hns3: add devlink reload support for PF Guangbin Huang
2021-07-26 2:47 ` [PATCH V3 net-next 7/7] net: hns3: add devlink reload support for VF Guangbin Huang
2021-07-26 11:30 ` [PATCH V3 net-next 0/7] net: hns3: add support devlink patchwork-bot+netdevbpf
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=1627267627-38467-2-git-send-email-huangguangbin2@huawei.com \
--to=huangguangbin2@huawei.com \
--cc=chenhao288@hisilicon.com \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lipeng321@huawei.com \
--cc=moyufeng@huawei.com \
--cc=netdev@vger.kernel.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 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.