netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, nic_swsd@realtek.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] r8169: improve jumbo configuration
Date: Tue, 12 Jan 2021 01:00:09 +0000	[thread overview]
Message-ID: <161041320916.15587.539634124247141136.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1dd337a0-ff5a-3fa0-91f5-45e86c0fce58@gmail.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Sat, 9 Jan 2021 22:59:08 +0100 you wrote:
> Small improvements to jumbo configuration.
> 
> Heiner Kallweit (2):
>   r8169: align RTL8168e jumbo pcie read request size with vendor driver
>   r8169: tweak max read request size for newer chips also in jumbo mtu
>     mode
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] r8169: align RTL8168e jumbo pcie read request size with vendor driver
    https://git.kernel.org/netdev/net-next/c/2007317e15cd
  - [net-next,2/2] r8169: tweak max read request size for newer chips also in jumbo mtu mode
    https://git.kernel.org/netdev/net-next/c/5e00e16cb989

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



      parent reply	other threads:[~2021-01-12  1:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09 21:59 [PATCH net-next 0/2] r8169: improve jumbo configuration Heiner Kallweit
2021-01-09 22:00 ` [PATCH net-next 1/2] r8169: align RTL8168e jumbo pcie read request size with vendor driver Heiner Kallweit
2021-01-09 22:01 ` [PATCH net-next 2/2] r8169: tweak max read request size for newer chips also in jumbo mtu mode Heiner Kallweit
2021-01-12  1: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=161041320916.15587.539634124247141136.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.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).