devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	edumazet@google.com, pabeni@redhat.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/6] tsnep: multi queue support and some other improvements
Date: Fri, 30 Sep 2022 11:00:17 +0000	[thread overview]
Message-ID: <166453561728.12525.13335744248938169663.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220927195842.44641-1-gerhard@engleder-embedded.com>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Tue, 27 Sep 2022 21:58:36 +0200 you wrote:
> Add support for additional TX/RX queues along with RX flow classification
> support.
> 
> Binding is extended to allow additional interrupts for additional TX/RX
> queues. Also dma-coherent is allowed as minor improvement.
> 
> RX path optimisation is done by using page pool as preparations for future
> XDP support.
> 
> [...]

Here is the summary with links:
  - [net-next,v4,1/6] dt-bindings: net: tsnep: Allow dma-coherent
    https://git.kernel.org/netdev/net-next/c/ff46c610abd6
  - [net-next,v4,2/6] dt-bindings: net: tsnep: Allow additional interrupts
    https://git.kernel.org/netdev/net-next/c/60e1b494ef88
  - [net-next,v4,3/6] tsnep: Move interrupt from device to queue
    (no matching commit)
  - [net-next,v4,4/6] tsnep: Support multiple TX/RX queue pairs
    https://git.kernel.org/netdev/net-next/c/762031375d5c
  - [net-next,v4,5/6] tsnep: Add EtherType RX flow classification support
    https://git.kernel.org/netdev/net-next/c/308ce1426509
  - [net-next,v4,6/6] tsnep: Use page pool for RX
    https://git.kernel.org/netdev/net-next/c/bb837a37db8d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-09-30 11:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 19:58 [PATCH net-next v4 0/6] tsnep: multi queue support and some other improvements Gerhard Engleder
2022-09-27 19:58 ` [PATCH net-next v4 1/6] dt-bindings: net: tsnep: Allow dma-coherent Gerhard Engleder
2022-09-30 14:41   ` Rob Herring
2022-09-27 19:58 ` [PATCH net-next v4 2/6] dt-bindings: net: tsnep: Allow additional interrupts Gerhard Engleder
2022-09-30 14:42   ` Rob Herring
2022-09-27 19:58 ` [PATCH net-next v4 3/6] tsnep: Move interrupt from device to queue Gerhard Engleder
2022-09-27 19:58 ` [PATCH net-next v4 4/6] tsnep: Support multiple TX/RX queue pairs Gerhard Engleder
2022-09-27 19:58 ` [PATCH net-next v4 5/6] tsnep: Add EtherType RX flow classification support Gerhard Engleder
2022-09-27 19:58 ` [PATCH net-next v4 6/6] tsnep: Use page pool for RX Gerhard Engleder
2022-09-30 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=166453561728.12525.13335744248938169663.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=gerhard@engleder-embedded.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh+dt@kernel.org \
    /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).