netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Linu Cherian <lcherian@marvell.com>
Cc: <davem@davemloft.net>, <sgoutham@marvell.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<gakula@marvell.com>, <hkelam@marvell.com>, <sbhatta@marvell.com>,
	<edumazet@google.com>, <pabeni@redhat.com>
Subject: Re: [PATCH v2 net-next 0/2] octeontx2: Few debugfs enhancements
Date: Fri, 13 Sep 2024 21:43:37 -0700	[thread overview]
Message-ID: <20240913214337.50c18fad@kernel.org> (raw)
In-Reply-To: <20240912161450.164402-1-lcherian@marvell.com>

On Thu, 12 Sep 2024 21:44:48 +0530 Linu Cherian wrote:
> Patch 1 adds a devlink param to enable/disable counters for default
> rules. Once enabled, counters can be read from the debugfs files 
> 
> Patch 2 adds channel info to the existing device - RPM map debugfs files  

We're closing up the 6.12 release, there isn't enough time to think
thru patch 1, but patch 2 looks fairly straightforward so I'll apply
just that. Please repost patch 1 when net-next reopens.

  parent reply	other threads:[~2024-09-14  4:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 16:14 [PATCH v2 net-next 0/2] octeontx2: Few debugfs enhancements Linu Cherian
2024-09-12 16:14 ` [PATCH v2 net-next 1/2] octeontx2-af: Knobs for NPC default rule counters Linu Cherian
2024-09-14  8:13   ` Simon Horman
2024-09-17  4:38     ` Linu Cherian
2024-09-17  8:12       ` Simon Horman
2024-09-12 16:14 ` [PATCH v2 net-next 2/2] octeontx2-af: debugfs: Add Channel info to RPM map Linu Cherian
2024-09-14  4:43 ` Jakub Kicinski [this message]
2024-09-14  4:50 ` [PATCH v2 net-next 0/2] octeontx2: Few debugfs enhancements 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=20240913214337.50c18fad@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=lcherian@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).