From: Rakesh Babu <rsaladi2@marvell.com>
To: <sgoutham@marvell.com>, <gakula@marvell.com>,
<sbhatta@marvell.com>, <hkelam@marvell.com>,
<davem@davemloft.net>, <kuba@kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Rakesh Babu <rsaladi2@marvell.com>
Subject: [net-next PATCH v2 0/3] RVU Debugfs updates.
Date: Tue, 26 Oct 2021 17:48:11 +0530 [thread overview]
Message-ID: <20211026121814.27036-1-rsaladi2@marvell.com> (raw)
The following patch series consists of the changes/modifications that are
newly added/done to rvu_debugfs.c file.
Patch 1: Few minor changes such as spelling mistakes, deleting unwanted
characters, etc.
Patch 2: Add debugfs dump for lmtst map table
Patch 3: Add channel and channel mask in debugfs.
Changes made from v1 to v2
1. In patch 1 removed unnecessary change, updated commit message.
2. In patch 2 updated commit message explaining about what is LMTST map
table.
3. Patch 3 is left unchanged.
Harman Kalra (1):
octeontx2-af: cn10k: debugfs for dumping LMTST map table
Rakesh Babu (2):
octeontx2-af: debugfs: Minor changes.
octeontx2-af: debugfs: Add channel and channel mask.
.../net/ethernet/marvell/octeontx2/af/npc.h | 4 +
.../marvell/octeontx2/af/rvu_debugfs.c | 120 ++++++++++++++++--
.../ethernet/marvell/octeontx2/af/rvu_nix.c | 3 +
.../marvell/octeontx2/af/rvu_npc_fs.c | 3 +
4 files changed, 118 insertions(+), 12 deletions(-)
--
2.17.1
next reply other threads:[~2021-10-26 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 12:18 Rakesh Babu [this message]
2021-10-26 12:18 ` [net-next PATCH v2 1/3] octeontx2-af: debugfs: Minor changes Rakesh Babu
2021-10-26 21:13 ` Jakub Kicinski
2021-10-26 12:18 ` [net-next PATCH v2 2/3] octeontx2-af: cn10k: debugfs for dumping LMTST map table Rakesh Babu
2021-10-26 12:18 ` [net-next PATCH v2 3/3] octeontx2-af: debugfs: Add channel and channel mask Rakesh Babu
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=20211026121814.27036-1-rsaladi2@marvell.com \
--to=rsaladi2@marvell.com \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
/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.