From: patchwork-bot+netdevbpf@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,
edumazet@google.com, sgoutham@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com
Subject: Re: [PATCH v2 0/2] Dynamically allocate BPIDs for LBK
Date: Fri, 02 Feb 2024 12:20:29 +0000 [thread overview]
Message-ID: <170687642987.27809.15518970048126764791.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240131075441.17227-1-gakula@marvell.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 31 Jan 2024 13:24:39 +0530 you wrote:
> In current driver 64 BPIDs are reserved for LBK interfaces.
> These bpids are 1-to-1 mapped to LBK interface channel numbers.
> In some usecases one LBK interface required more than one bpids
> and in some case they may not require at all. These usescas
> can't be address with the current implementation as it always
> reserves only one bpid per LBK channel.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] octeontx2-af: Create BPIDs free pool
https://git.kernel.org/netdev/net-next/c/d6212d2e41a0
- [net-next,v2,2/2] octeontx2-af: Cleanup loopback device checks
https://git.kernel.org/netdev/net-next/c/ae703539f49d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-02-02 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 7:54 [PATCH v2 0/2] Dynamically allocate BPIDs for LBK Geetha sowjanya
2024-01-31 7:54 ` [net-next v2 PATCH 1/2] octeontx2-af: Create BPIDs free pool Geetha sowjanya
2024-01-31 7:54 ` [net-next v2 PATCH 2/2] octeontx2-af: Cleanup loopback device checks Geetha sowjanya
2024-01-31 9:52 ` [PATCH v2 0/2] Dynamically allocate BPIDs for LBK Jiri Pirko
2024-02-02 12:20 ` patchwork-bot+netdevbpf [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=170687642987.27809.15518970048126764791.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).