From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, ast@kernel.org,
daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.co,
linux@armlinux.org.uk, alexandr.lobakin@intel.com,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v3 0/4] net: lan966x: Add xdp support
Date: Fri, 11 Nov 2022 11:00:16 +0000 [thread overview]
Message-ID: <166816441667.11358.7443670994453158493.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221109204613.3669905-1-horatiu.vultur@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 9 Nov 2022 21:46:09 +0100 you wrote:
> Add support for xdp in lan966x driver. Currently only XDP_PASS and
> XDP_DROP are supported.
>
> The first 2 patches are just moving things around just to simplify
> the code for when the xdp is added.
> Patch 3 actually adds the xdp. Currently the only supported actions
> are XDP_PASS and XDP_DROP. In the future this will be extended with
> XDP_TX and XDP_REDIRECT.
> Patch 4 changes to use page pool API, because the handling of the
> pages is similar with what already lan966x driver is doing. In this
> way is possible to remove some of the code.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/4] net: lan966x: Add define IFH_LEN_BYTES
https://git.kernel.org/netdev/net-next/c/e83163b66a37
- [net-next,v3,2/4] net: lan966x: Split function lan966x_fdma_rx_get_frame
https://git.kernel.org/netdev/net-next/c/4a00b0c712e3
- [net-next,v3,3/4] net: lan966x: Add basic XDP support
https://git.kernel.org/netdev/net-next/c/6a2159be7604
- [net-next,v3,4/4] net: lan96x: Use page_pool API
https://git.kernel.org/netdev/net-next/c/11871aba1974
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:[~2022-11-11 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 20:46 [PATCH net-next v3 0/4] net: lan966x: Add xdp support Horatiu Vultur
2022-11-09 20:46 ` [PATCH net-next v3 1/4] net: lan966x: Add define IFH_LEN_BYTES Horatiu Vultur
2022-11-09 20:46 ` [PATCH net-next v3 2/4] net: lan966x: Split function lan966x_fdma_rx_get_frame Horatiu Vultur
2022-11-09 20:46 ` [PATCH net-next v3 3/4] net: lan966x: Add basic XDP support Horatiu Vultur
2022-11-09 20:46 ` [PATCH net-next v3 4/4] net: lan96x: Use page_pool API Horatiu Vultur
2022-11-10 11:17 ` [PATCH net-next v3 0/4] net: lan966x: Add xdp support Alexander Lobakin
2022-11-10 13:57 ` Andrew Lunn
2022-11-10 16:21 ` Alexander Lobakin
2022-11-10 20:21 ` Horatiu Vultur
2022-11-10 22:51 ` Andrew Lunn
2022-11-11 11:00 ` 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=166816441667.11358.7443670994453158493.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandr.lobakin@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=john.fastabend@gmail.co \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).