netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Riyan Dhiman <riyandhiman14@gmail.com>
Cc: sgoutham@marvell.com, lcherian@marvell.com, gakula@marvell.com,
	jerinj@marvell.com, hkelam@marvell.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	rsaladi2@marvell.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] octeontx2-af: Change block parameter to const pointer in get_lf_str_list
Date: Thu, 19 Sep 2024 16:10:11 +0100	[thread overview]
Message-ID: <20240919151011.GG1571683@kernel.org> (raw)
In-Reply-To: <20240919091935.68209-2-riyandhiman14@gmail.com>

On Thu, Sep 19, 2024 at 02:49:36PM +0530, Riyan Dhiman wrote:
> Convert struct rvu_block block to const struct rvu_block *block in
> get_lf_str_list() function parameter. This improves efficiency by
> avoiding structure copying and reflects the function's read-only
> access to block.
> 
> Fixes: e77bcdd1f639 (octeontx2-af: Display all enabled PF VF rsrc_alloc entries.)
> Signed-off-by: Riyan Dhiman <riyandhiman14@gmail.com>

Hi Riyan,

Thanks for your patch.

While I agree that this is a nice change I don't feel that it is
a fix, typically something that addresses a user-visible bug.

I suggest that the patch should be treated as an enhancement.
It should not have a Fixes tag. And it should be targeted at
net-next (as opposed to net, which is, in general, for fixes).

	Subject: [PATCH net-next] ...

Please note that net-next is currently closed for the v6.12 merge window.
It should reopen after v6.12-rc1 has been released, likely during
the week of the 30th September.

So please consider reposting your patch once net-next has reopened.

Link: https://docs.kernel.org/process/maintainer-netdev.html

-- 
pw-bot: defer

      reply	other threads:[~2024-09-19 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19  9:19 [PATCH] octeontx2-af: Change block parameter to const pointer in get_lf_str_list Riyan Dhiman
2024-09-19 15:10 ` Simon Horman [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=20240919151011.GG1571683@kernel.org \
    --to=horms@kernel.org \
    --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=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=riyandhiman14@gmail.com \
    --cc=rsaladi2@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).