From: Simon Horman <horms@kernel.org>
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,
jiri@resnulli.us, edumazet@google.com, sgoutham@marvell.com,
sbhatta@marvell.com, hkelam@marvell.com
Subject: Re: [net-next PATCH v4 4/4] octeontx2-pf: Move shared APIs to header file
Date: Thu, 24 Oct 2024 16:00:10 +0100 [thread overview]
Message-ID: <20241024150010.GS1202098@kernel.org> (raw)
In-Reply-To: <20241023161843.15543-5-gakula@marvell.com>
On Wed, Oct 23, 2024 at 09:48:43PM +0530, Geetha sowjanya wrote:
> Move mbox, hw resources and interrupt configuration functions to common
> header file. So, that they can be used later by the RVU representor driver.
>
> Signed-off-by: Geetha sowjanya <gakula@marvell.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-10-24 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 16:18 [net-next PATCH v4 0/4] Refactoring RVU NIC driver Geetha sowjanya
2024-10-23 16:18 ` [net-next PATCH v4 1/4] octeontx2-pf: Define common API for HW resources configuration Geetha sowjanya
2024-10-24 15:03 ` Simon Horman
2024-10-23 16:18 ` [net-next PATCH v4 2/4] octeontx2-pf: Add new APIs for queue memory alloc/free Geetha sowjanya
2024-10-24 15:02 ` Simon Horman
2024-10-23 16:18 ` [net-next PATCH v4 3/4] octeontx2-pf: Reuse PF max mtu value Geetha sowjanya
2024-10-24 15:00 ` Simon Horman
2024-10-23 16:18 ` [net-next PATCH v4 4/4] octeontx2-pf: Move shared APIs to header file Geetha sowjanya
2024-10-24 15:00 ` Simon Horman [this message]
2024-10-31 0:52 ` [net-next PATCH v4 0/4] Refactoring RVU NIC driver Jakub Kicinski
2024-10-31 1:10 ` 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=20241024150010.GS1202098@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jiri@resnulli.us \
--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 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.