From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: davem@davemloft.net, andrew@lunn.ch, edumazet@google.com,
f.fainelli@gmail.com, kuba@kernel.org, pabeni@redhat.com,
olteanv@gmail.com, woojung.huh@microchip.com,
arun.ramadoss@microchip.com, kernel@pengutronix.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
UNGLinuxDriver@microchip.com, linux@armlinux.org.uk
Subject: Re: [PATCH net-next v2 0/5] Microchip DSA Driver Improvements
Date: Tue, 30 May 2023 09:41:32 +0000 [thread overview]
Message-ID: <168543969270.28717.11968516011003747192.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230526073445.668430-1-o.rempel@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 26 May 2023 09:34:40 +0200 you wrote:
> changes v2:
> - set .max_register = U8_MAX, it should be more readable
> - clarify in the RMW error handling patch, logging behavior
> expectation.
>
> I'd like to share a set of patches for the Microchip DSA driver. These
> patches were chosen from a bigger set because they are simpler and
> should be easier to review. The goal is to make the code easier to read,
> get rid of unused code, and handle errors better.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] net: dsa: microchip: improving error handling for 8-bit register RMW operations
https://git.kernel.org/netdev/net-next/c/2f0d579956e8
- [net-next,v2,2/5] net: dsa: microchip: add an enum for regmap widths
https://git.kernel.org/netdev/net-next/c/b8311f46c6f5
- [net-next,v2,3/5] net: dsa: microchip: remove ksz_port:on variable
https://git.kernel.org/netdev/net-next/c/bb4609d27f89
- [net-next,v2,4/5] net: dsa: microchip: ksz8: Prepare ksz8863_smi for regmap register access validation
https://git.kernel.org/netdev/net-next/c/ae1ad12e9da4
- [net-next,v2,5/5] net: dsa: microchip: Add register access control for KSZ8873 chip
https://git.kernel.org/netdev/net-next/c/d0dec3333040
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:[~2023-05-30 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 7:34 [PATCH net-next v2 0/5] Microchip DSA Driver Improvements Oleksij Rempel
2023-05-26 7:34 ` [PATCH net-next v2 1/5] net: dsa: microchip: improving error handling for 8-bit register RMW operations Oleksij Rempel
2023-05-26 7:34 ` [PATCH net-next v2 2/5] net: dsa: microchip: add an enum for regmap widths Oleksij Rempel
2023-05-26 7:34 ` [PATCH net-next v2 3/5] net: dsa: microchip: remove ksz_port:on variable Oleksij Rempel
2023-05-26 9:55 ` Vladimir Oltean
2023-05-26 7:34 ` [PATCH net-next v2 4/5] net: dsa: microchip: ksz8: Prepare ksz8863_smi for regmap register access validation Oleksij Rempel
2023-05-26 9:54 ` Vladimir Oltean
2023-05-26 7:34 ` [PATCH net-next v2 5/5] net: dsa: microchip: Add register access control for KSZ8873 chip Oleksij Rempel
2023-05-30 9:41 ` 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=168543969270.28717.11968516011003747192.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--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=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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