public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Geetha sowjanya <gakula@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
	edumazet@google.com, sgoutham@marvell.com, sbhatta@marvell.com,
	hkelam@marvell.com
Subject: Re: [net-next PATCH 1/4] octeontx2-pf: Defines common API for HW resources configuration
Date: Tue, 3 Sep 2024 16:55:07 +0200	[thread overview]
Message-ID: <ZtcjS5_acSWt5YGg@nanopsycho.orion> (raw)
In-Reply-To: <20240903124048.14235-2-gakula@marvell.com>

Tue, Sep 03, 2024 at 02:40:45PM CEST, gakula@marvell.com wrote:
>Defines new API "otx2_init_rsrc" and moves the HW blocks

s/Defines/Define/ (in subject of the patch as well)
s/moves/move/

Otherwise that patch looks ok.


>NIX/NPA resources configuration code under this API. So, that
>it can be used by the RVU representor driver that has similar
>resources of RVU NIC.
>
>Signed-off-by: Geetha sowjanya <gakula@marvell.com>

  reply	other threads:[~2024-09-03 14:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 12:40 [net-next PATCH 0/4] Refactoring RVU NIC driver Geetha sowjanya
2024-09-03 12:40 ` [net-next PATCH 1/4] octeontx2-pf: Defines common API for HW resources configuration Geetha sowjanya
2024-09-03 14:55   ` Jiri Pirko [this message]
2024-09-03 14:57   ` Pavan Chebbi
2024-09-04  5:48     ` [EXTERNAL] " Geethasowjanya Akula
2024-09-04  6:18       ` Pavan Chebbi
2024-09-03 12:40 ` [net-next PATCH 2/4] octeontx2-pf: Add new APIs for queue memory alloc/free Geetha sowjanya
2024-09-03 15:12   ` Pavan Chebbi
2024-09-04  5:35     ` [EXTERNAL] " Geethasowjanya Akula
2024-09-03 12:40 ` [net-next PATCH 3/4] octeontx2-pf: Reuse PF max mtu value Geetha sowjanya
2024-09-03 12:40 ` [net-next PATCH 4/4] octeontx2-pf: Export common APIs Geetha sowjanya
2024-09-03 15:00   ` Jiri Pirko
2024-09-04  6:20     ` [EXTERNAL] " Geethasowjanya Akula

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=ZtcjS5_acSWt5YGg@nanopsycho.orion \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=kuba@kernel.org \
    --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