All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-usb@vger.kernel.org, michael.jamet@intel.com,
	YehezkelShB@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, andreas.noever@gmail.com,
	lukas@wunner.de, netdev@vger.kernel.org
Subject: Re: [PATCH 0/5] thunderbolt: net: Enable full end-to-end flow control
Date: Wed, 31 Aug 2022 13:20:16 +0000	[thread overview]
Message-ID: <166195201641.2919.1480626545715329070.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220830153250.15496-1-mika.westerberg@linux.intel.com>

Hello:

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

On Tue, 30 Aug 2022 18:32:45 +0300 you wrote:
> Hi all,
> 
> Thunderbolt/USB4 host controllers support full end-to-end flow control
> that prevents dropping packets if there are not enough hardware receive
> buffers. So far it has not been enabled for the networking driver yet
> but this series changes that. There is one snag though: the second
> generation (Intel Falcon Ridge) had a bug that needs special quirk to
> get it working. We had that in the early stages of the Thunderbolt/USB4
> driver but it got dropped because it was not needed at the time. Now we
> add it back as a quirk for the host controller (NHI).
> 
> [...]

Here is the summary with links:
  - [1/5] net: thunderbolt: Enable DMA paths only after rings are enabled
    https://git.kernel.org/netdev/net-next/c/ff7cd07f3064
  - [2/5] thunderbolt: Show link type for XDomain connections too
    https://git.kernel.org/netdev/net-next/c/f9cad07b840e
  - [3/5] thunderbolt: Add back Intel Falcon Ridge end-to-end flow control workaround
    https://git.kernel.org/netdev/net-next/c/54669e2f17cb
  - [4/5] net: thunderbolt: Enable full end-to-end flow control
    https://git.kernel.org/netdev/net-next/c/8bdc25cf62c7
  - [5/5] net: thunderbolt: Update module description with mention of USB4
    https://git.kernel.org/netdev/net-next/c/e550ed4b87ad

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-08-31 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 15:32 [PATCH 0/5] thunderbolt: net: Enable full end-to-end flow control Mika Westerberg
2022-08-30 15:32 ` [PATCH 1/5] net: thunderbolt: Enable DMA paths only after rings are enabled Mika Westerberg
2022-08-30 15:32 ` [PATCH 2/5] thunderbolt: Show link type for XDomain connections too Mika Westerberg
2022-08-30 15:32 ` [PATCH 3/5] thunderbolt: Add back Intel Falcon Ridge end-to-end flow control workaround Mika Westerberg
2022-08-30 15:32 ` [PATCH 4/5] net: thunderbolt: Enable full end-to-end flow control Mika Westerberg
2022-08-30 15:32 ` [PATCH 5/5] net: thunderbolt: Update module description with mention of USB4 Mika Westerberg
2022-08-31 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=166195201641.2919.1480626545715329070.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --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.