From: Simon Horman <horms@kernel.org>
To: Hariprasad Kelam <hkelam@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kuba@kernel.org, davem@davemloft.net, sgoutham@marvell.com,
gakula@marvell.com, jerinj@marvell.com, lcherian@marvell.com,
sbhatta@marvell.com, naveenm@marvell.com, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, bbhushan2@marvell.com
Subject: Re: [net-next PatchV2 4/4] Octeontx2-af: Debugfs support for firmware data
Date: Sun, 20 Jul 2025 19:10:05 +0100 [thread overview]
Message-ID: <20250720181005.GX2459@horms.kernel.org> (raw)
In-Reply-To: <20250720163638.1560323-5-hkelam@marvell.com>
On Sun, Jul 20, 2025 at 10:06:38PM +0530, Hariprasad Kelam wrote:
> MAC address, Link modes (supported and advertised) and eeprom data
> for the Netdev interface are read from the shared firmware data.
> This patch adds debugfs support for the same.
>
> Signed-off-by: Hariprasad Kelam <hkelam@marvell.com>
> ---
> V2 *
> fix max line length warnings and typo
Thanks for the update.
next prev parent reply other threads:[~2025-07-20 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-20 16:36 [net-next PatchV2 0/4] Octeontx2-af: RPM: misc feaures Hariprasad Kelam
2025-07-20 16:36 ` [net-next PatchV2 1/4] Octeontx2-af: Add programmed macaddr to RVU pfvf Hariprasad Kelam
2025-07-20 18:10 ` Simon Horman
2025-07-20 16:36 ` [net-next PatchV2 2/4] Octeontx2-af: Disable stale DMAC filters Hariprasad Kelam
2025-07-20 16:36 ` [net-next PatchV2 3/4] Octeontx2-af: RPM: Update DMA mask Hariprasad Kelam
2025-07-20 16:36 ` [net-next PatchV2 4/4] Octeontx2-af: Debugfs support for firmware data Hariprasad Kelam
2025-07-20 18:10 ` Simon Horman [this message]
2025-07-23 19:10 ` Kees Bakker
2025-07-22 13:40 ` [net-next PatchV2 0/4] Octeontx2-af: RPM: misc feaures 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=20250720181005.GX2459@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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.