From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, vivien.didelot@gmail.com,
f.fainelli@gmail.com, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, colin.foster@in-advantage.com,
fido_max@inbox.ru
Subject: Re: [PATCH net-next 0/5] Rework resource allocation in Felix DSA driver
Date: Thu, 29 Sep 2022 02:50:25 +0000 [thread overview]
Message-ID: <166441982546.2371.1761318853116155565.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220927191521.1578084-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Sep 2022 22:15:15 +0300 you wrote:
> The Felix DSA driver controls NXP variations of Microchip switches.
> Colin Foster is trying to add support in this driver for "genuine"
> Microchip hardware, but some of the NXP-isms in this driver need to go
> away before that happens cleanly.
> https://patchwork.kernel.org/project/netdevbpf/cover/20220926002928.2744638-1-colin.foster@in-advantage.com/
>
> The starting point was Colin's patch 08/14 "net: dsa: felix: update
> init_regmap to be string-based", and this continues to be the central
> theme here, but things are done differently.
>
> [...]
Here is the summary with links:
- [net-next,1/5] net: dsa: felix: remove felix_info :: imdio_res
https://git.kernel.org/netdev/net-next/c/5fc080de89f1
- [net-next,2/5] net: dsa: felix: remove felix_info :: imdio_base
https://git.kernel.org/netdev/net-next/c/1382ba68a053
- [net-next,3/5] net: dsa: felix: remove felix_info :: init_regmap
https://git.kernel.org/netdev/net-next/c/8f66c64bfca3
- [net-next,4/5] net: dsa: felix: use DEFINE_RES_MEM_NAMED for resources
https://git.kernel.org/netdev/net-next/c/044d447a801f
- [net-next,5/5] net: dsa: felix: update init_regmap to be string-based
https://git.kernel.org/netdev/net-next/c/1109b97b6161
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-09-29 2:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 19:15 [PATCH net-next 0/5] Rework resource allocation in Felix DSA driver Vladimir Oltean
2022-09-27 19:15 ` [PATCH net-next 1/5] net: dsa: felix: remove felix_info :: imdio_res Vladimir Oltean
2022-09-27 19:15 ` [PATCH net-next 2/5] net: dsa: felix: remove felix_info :: imdio_base Vladimir Oltean
2022-09-27 19:15 ` [PATCH net-next 3/5] net: dsa: felix: remove felix_info :: init_regmap Vladimir Oltean
2022-09-27 19:15 ` [PATCH net-next 4/5] net: dsa: felix: use DEFINE_RES_MEM_NAMED for resources Vladimir Oltean
2022-09-27 19:15 ` [PATCH net-next 5/5] net: dsa: felix: update init_regmap to be string-based Vladimir Oltean
2022-09-27 19:27 ` Vladimir Oltean
2022-09-27 23:51 ` Jakub Kicinski
2022-09-27 19:15 ` [PATCH net-next 5/5] net: dsa: felix: update regmap requests " Vladimir Oltean
2022-09-27 20:28 ` Colin Foster
2022-09-29 2:50 ` 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=166441982546.2371.1761318853116155565.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=fido_max@inbox.ru \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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).