All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: nic_swsd@realtek.com, pabeni@redhat.com, kuba@kernel.org,
	davem@davemloft.net, edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] r8169: enable SG/TSO on selected chip versions per default
Date: Mon, 14 Oct 2024 12:20:30 +0000	[thread overview]
Message-ID: <172890843000.494844.8256084079732573006.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <5daec1ce-1956-4ed2-b2ad-9ac05627ae8f@gmail.com>

Hello:

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

On Thu, 10 Oct 2024 12:58:02 +0200 you wrote:
> Due to problem reports in the past SG and TSO/TSO6 are disabled per
> default. It's not fully clear which chip versions are affected, so we
> may impact also users of unaffected chip versions, unless they know
> how to use ethtool for enabling SG/TSO/TSO6.
> Vendor drivers r8168/r8125 enable SG/TSO/TSO6 for selected chip
> versions per default, I'd interpret this as confirmation that these
> chip versions are unaffected. So let's do the same here.
> 
> [...]

Here is the summary with links:
  - [net-next] r8169: enable SG/TSO on selected chip versions per default
    https://git.kernel.org/netdev/net-next/c/b8bf38440ba9

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



      parent reply	other threads:[~2024-10-14 12:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 10:58 [PATCH net-next] r8169: enable SG/TSO on selected chip versions per default Heiner Kallweit
2024-10-11  8:57 ` Simon Horman
2024-10-14 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=172890843000.494844.8256084079732573006.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --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.