From: patchwork-bot+netdevbpf@kernel.org
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: netdev@vger.kernel.org, alexander.duyck@gmail.com,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com
Subject: Re: [PATCH net-next v5 0/9] tsnep: XDP support
Date: Wed, 18 Jan 2023 13:20:18 +0000 [thread overview]
Message-ID: <167404801867.10842.12920748675264358351.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230116202458.56677-1-gerhard@engleder-embedded.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 16 Jan 2023 21:24:49 +0100 you wrote:
> Implement XDP support for tsnep driver. I tried to follow existing
> drivers like igb/igc as far as possible. Some prework was already done
> in previous patch series, so in this series only actual XDP stuff is
> included.
>
> Thanks for the NetDev 0x14 slides "Add XDP support on a NIC driver".
>
> [...]
Here is the summary with links:
- [net-next,v5,1/9] tsnep: Replace TX spin_lock with __netif_tx_lock
https://git.kernel.org/netdev/net-next/c/25faa6a4c5ca
- [net-next,v5,2/9] tsnep: Forward NAPI budget to napi_consume_skb()
https://git.kernel.org/netdev/net-next/c/0625dff38b17
- [net-next,v5,3/9] tsnep: Do not print DMA mapping error
https://git.kernel.org/netdev/net-next/c/95337b938476
- [net-next,v5,4/9] tsnep: Add XDP TX support
https://git.kernel.org/netdev/net-next/c/d24bc0bcbbff
- [net-next,v5,5/9] tsnep: Subtract TSNEP_RX_INLINE_METADATA_SIZE once
https://git.kernel.org/netdev/net-next/c/59d562aa1983
- [net-next,v5,6/9] tsnep: Prepare RX buffer for XDP support
https://git.kernel.org/netdev/net-next/c/cc3e254f9443
- [net-next,v5,7/9] tsnep: Add RX queue info for XDP support
https://git.kernel.org/netdev/net-next/c/e77832abd90a
- [net-next,v5,8/9] tsnep: Add XDP RX support
https://git.kernel.org/netdev/net-next/c/65b28c810035
- [net-next,v5,9/9] tsnep: Support XDP BPF program setup
https://git.kernel.org/netdev/net-next/c/f0f6460f9130
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:[~2023-01-18 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 20:24 [PATCH net-next v5 0/9] tsnep: XDP support Gerhard Engleder
2023-01-16 20:24 ` [PATCH net-next v5 1/9] tsnep: Replace TX spin_lock with __netif_tx_lock Gerhard Engleder
2023-01-16 20:24 ` [PATCH net-next v5 2/9] tsnep: Forward NAPI budget to napi_consume_skb() Gerhard Engleder
2023-01-16 20:24 ` [PATCH net-next v5 3/9] tsnep: Do not print DMA mapping error Gerhard Engleder
2023-01-16 20:24 ` [PATCH net-next v5 4/9] tsnep: Add XDP TX support Gerhard Engleder
2023-01-16 20:24 ` [PATCH net-next v5 5/9] tsnep: Subtract TSNEP_RX_INLINE_METADATA_SIZE once Gerhard Engleder
2023-01-16 20:24 ` [PATCH net-next v5 6/9] tsnep: Prepare RX buffer for XDP support Gerhard Engleder
2023-01-16 20:24 ` [PATCH net-next v5 7/9] tsnep: Add RX queue info " Gerhard Engleder
2023-01-16 20:24 ` [PATCH net-next v5 8/9] tsnep: Add XDP RX support Gerhard Engleder
2023-01-16 20:24 ` [PATCH net-next v5 9/9] tsnep: Support XDP BPF program setup Gerhard Engleder
2023-01-18 13: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=167404801867.10842.12920748675264358351.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gerhard@engleder-embedded.com \
--cc=kuba@kernel.org \
--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 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.