From: Subbaraya Sundeep <sbhatta@marvell.com>
To: Simon Horman <horms@kernel.org>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<gakula@marvell.com>, <hkelam@marvell.com>,
<sgoutham@marvell.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] octeontx2-pf: Do not reallocate all ntuple filters
Date: Fri, 9 May 2025 04:38:40 +0000 [thread overview]
Message-ID: <aB2G0MdH-NEMteKr@ce1afb5360f2> (raw)
In-Reply-To: <20250508185731.GO3339421@horms.kernel.org>
Hi Simon,
On 2025-05-08 at 18:57:31, Simon Horman (horms@kernel.org) wrote:
> On Wed, May 07, 2025 at 10:42:56PM +0530, Subbaraya Sundeep wrote:
> > If ntuple filters count is modified followed by
> > unicast filters count using devlink then the ntuple count
> > set by user is ignored and all the ntuple filters are
> > being reallocated. Fix this by storing the ntuple count
> > set by user using devlink.
> >
> > Fixes: 39c469188b6d ("octeontx2-pf: Add ucast filter count configurability via devlink.")
> > Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
>
> Hi Subbaraya,
>
> I am wondering if this is more of a but fix or more of a cleanup.
>
> If it is a bug then I think an explanation of how it manifests is
> warranted, and the patch should be targeted at net. If not, the Fixes tag
> should be dropped, and the patch should be targeted at net-next.
These patches target net indeed. My bad I missed net prefix in subject.
I will send v2 with net prefix.
Thanks,
Sundeep
>
> ...
prev parent reply other threads:[~2025-05-09 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 17:12 [PATCH] octeontx2-pf: Do not reallocate all ntuple filters Subbaraya Sundeep
2025-05-08 18:57 ` Simon Horman
2025-05-09 4:38 ` Subbaraya Sundeep [this message]
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=aB2G0MdH-NEMteKr@ce1afb5360f2 \
--to=sbhatta@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).