All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Linus Walleij <linus.walleij@linaro.org>
Cc: alsi@bang-olufsen.dk, andrew@lunn.ch, f.fainelli@gmail.com,
	olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: dsa: realtek: Two RTL8366RB fixes
Date: Tue, 12 Dec 2023 13:30:25 +0000	[thread overview]
Message-ID: <170238782595.14412.3820310748559815932.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231209-rtl8366rb-mtu-fix-v1-0-df863e2b2b2a@linaro.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Sat, 09 Dec 2023 23:37:33 +0100 you wrote:
> These minor fixes were found while digging into other
> issues: a weirdly named variable and bogus MTU handling.
> Fix it up.
> 
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Linus Walleij (2):
>       net: dsa: realtek: Rename bogus RTL8368S variable
>       net: dsa: realtek: Rewrite RTL8366RB MTU handling
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] net: dsa: realtek: Rename bogus RTL8368S variable
    https://git.kernel.org/netdev/net-next/c/389119c84218
  - [net-next,2/2] net: dsa: realtek: Rewrite RTL8366RB MTU handling
    https://git.kernel.org/netdev/net-next/c/d577ca429af3

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



      parent reply	other threads:[~2023-12-12 13:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-09 22:37 [PATCH net-next 0/2] net: dsa: realtek: Two RTL8366RB fixes Linus Walleij
2023-12-09 22:37 ` [PATCH net-next 1/2] net: dsa: realtek: Rename bogus RTL8368S variable Linus Walleij
2023-12-10 13:00   ` Alvin Šipraga
2023-12-11  2:50   ` Luiz Angelo Daros de Luca
2023-12-11 21:24   ` Florian Fainelli
2023-12-09 22:37 ` [PATCH net-next 2/2] net: dsa: realtek: Rewrite RTL8366RB MTU handling Linus Walleij
2023-12-10 13:00   ` Alvin Šipraga
2023-12-11  3:14   ` Luiz Angelo Daros de Luca
2023-12-11 15:30     ` Vladimir Oltean
2023-12-11 21:07       ` Luiz Angelo Daros de Luca
2023-12-12 13:01         ` Vladimir Oltean
2023-12-11 21:24   ` Florian Fainelli
2023-12-12 13:16   ` Paolo Abeni
2023-12-12 13:18     ` Paolo Abeni
2023-12-12 13:30 ` 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=170238782595.14412.3820310748559815932.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alsi@bang-olufsen.dk \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.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.