From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, kernel@pengutronix.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Arun.Ramadoss@microchip.com
Subject: Re: [PATCH net-next v7 0/6] net: dsa: microchip: add MTU support for KSZ8 series
Date: Wed, 07 Dec 2022 11:10:16 +0000 [thread overview]
Message-ID: <167041141656.12492.16254467680010942896.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221205052232.2834166-1-o.rempel@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 5 Dec 2022 06:22:26 +0100 you wrote:
> changes v7:
> - add Acked-bys and Reviewed-bys
>
> changes v6:
> - move dsa configuration to ksz8_setup
>
> changes v5:
> - add mtu normalization patch
>
> [...]
Here is the summary with links:
- [net-next,v7,1/6] net: dsa: microchip: move max mtu to one location
https://git.kernel.org/netdev/net-next/c/838c19f89454
- [net-next,v7,2/6] net: dsa: microchip: do not store max MTU for all ports
https://git.kernel.org/netdev/net-next/c/1d0a1a6d0d63
- [net-next,v7,3/6] net: dsa: microchip: add ksz_rmw8() function
https://git.kernel.org/netdev/net-next/c/6f1b986a43ce
- [net-next,v7,4/6] net: dsa: microchip: ksz8: add MTU configuration support
https://git.kernel.org/netdev/net-next/c/29d1e85f45e0
- [net-next,v7,5/6] net: dsa: microchip: enable MTU normalization for KSZ8795 and KSZ9477 compatible switches
https://git.kernel.org/netdev/net-next/c/6b30cfa86ee7
- [net-next,v7,6/6] net: dsa: microchip: ksz8: move all DSA configurations to one location
https://git.kernel.org/netdev/net-next/c/55a952eef70a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-12-07 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 5:22 [PATCH net-next v7 0/6] net: dsa: microchip: add MTU support for KSZ8 series Oleksij Rempel
2022-12-05 5:22 ` [PATCH net-next v7 1/6] net: dsa: microchip: move max mtu to one location Oleksij Rempel
2022-12-05 5:22 ` [PATCH net-next v7 2/6] net: dsa: microchip: do not store max MTU for all ports Oleksij Rempel
2022-12-05 5:22 ` [PATCH net-next v7 3/6] net: dsa: microchip: add ksz_rmw8() function Oleksij Rempel
2022-12-05 5:22 ` [PATCH net-next v7 4/6] net: dsa: microchip: ksz8: add MTU configuration support Oleksij Rempel
2022-12-05 5:22 ` [PATCH net-next v7 5/6] net: dsa: microchip: enable MTU normalization for KSZ8795 and KSZ9477 compatible switches Oleksij Rempel
2022-12-05 5:22 ` [PATCH net-next v7 6/6] net: dsa: microchip: ksz8: move all DSA configurations to one location Oleksij Rempel
2022-12-07 11:10 ` 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=167041141656.12492.16254467680010942896.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Arun.Ramadoss@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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