From: patchwork-bot+netdevbpf@kernel.org
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: robh@kernel.org, linux-kernel@vger.kernel.org, npiggin@gmail.com,
edumazet@google.com, netdev@vger.kernel.org, kuba@kernel.org,
pabeni@redhat.com, linuxppc-dev@lists.ozlabs.org,
davem@davemloft.net
Subject: Re: [PATCH net-next v2 00/10] net: fs_enet: Driver cleanup
Date: Tue, 08 Aug 2023 22:10:26 +0000 [thread overview]
Message-ID: <169153262641.13746.13289621238747032969.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1691155346.git.christophe.leroy@csgroup.eu>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 4 Aug 2023 15:30:10 +0200 you wrote:
> Over the years, platform and driver initialisation have evolved into
> more generic ways, and driver or platform specific stuff has gone
> away, leaving stale objects behind.
>
> This series aims at cleaning all that up for fs_enet ethernet driver.
>
> Changes in v2:
> - Remove a trailing whitespace in the old struct moved in patch 7.
> - Include powerpc people and list that I forgot when sending v1
> (and Rob as expected by Patchwork for patch 6, not sure why)
>
> [...]
Here is the summary with links:
- [net-next,v2,01/10] net: fs_enet: Remove set but not used variable
https://git.kernel.org/netdev/net-next/c/78d3902795f0
- [net-next,v2,02/10] net: fs_enet: Fix address space and base types mismatches
https://git.kernel.org/netdev/net-next/c/ae9e78a9dc88
- [net-next,v2,03/10] net: fs_enet: Remove fs_get_id()
https://git.kernel.org/netdev/net-next/c/26bbbef8ff40
- [net-next,v2,04/10] net: fs_enet: Remove unused fields in fs_platform_info struct
https://git.kernel.org/netdev/net-next/c/caaf482e2654
- [net-next,v2,05/10] net: fs_enet: Remove has_phy field in fs_platform_info struct
https://git.kernel.org/netdev/net-next/c/9359a48c65a3
- [net-next,v2,06/10] net: fs_enet: Remove stale prototypes from fsl_soc.c
https://git.kernel.org/netdev/net-next/c/62e106c802c5
- [net-next,v2,07/10] net: fs_enet: Move struct fs_platform_info into fs_enet.h
https://git.kernel.org/netdev/net-next/c/7a76918371fe
- [net-next,v2,08/10] net: fs_enet: Don't include fs_enet_pd.h when not needed
https://git.kernel.org/netdev/net-next/c/33deffc9f19f
- [net-next,v2,09/10] net: fs_enet: Remove linux/fs_enet_pd.h
https://git.kernel.org/netdev/net-next/c/7149b38dc7cb
- [net-next,v2,10/10] net: fs_enet: Use cpm_muram_xxx() functions instead of cpm_dpxxx() macros
https://git.kernel.org/netdev/net-next/c/5e6cb39a256d
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-08-08 22:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 13:30 [PATCH net-next v2 00/10] net: fs_enet: Driver cleanup Christophe Leroy
2023-08-04 13:30 ` [PATCH net-next v2 01/10] net: fs_enet: Remove set but not used variable Christophe Leroy
2023-08-04 13:30 ` [PATCH net-next v2 02/10] net: fs_enet: Fix address space and base types mismatches Christophe Leroy
2023-08-04 13:30 ` [PATCH net-next v2 03/10] net: fs_enet: Remove fs_get_id() Christophe Leroy
2023-08-04 13:30 ` [PATCH net-next v2 04/10] net: fs_enet: Remove unused fields in fs_platform_info struct Christophe Leroy
2023-08-04 13:30 ` [PATCH net-next v2 05/10] net: fs_enet: Remove has_phy field " Christophe Leroy
2023-08-04 13:30 ` [PATCH net-next v2 06/10] net: fs_enet: Remove stale prototypes from fsl_soc.c Christophe Leroy
2023-08-04 13:30 ` [PATCH net-next v2 07/10] net: fs_enet: Move struct fs_platform_info into fs_enet.h Christophe Leroy
2023-08-04 13:30 ` [PATCH net-next v2 08/10] net: fs_enet: Don't include fs_enet_pd.h when not needed Christophe Leroy
2023-08-04 13:30 ` [PATCH net-next v2 09/10] net: fs_enet: Remove linux/fs_enet_pd.h Christophe Leroy
2023-08-04 13:30 ` [PATCH net-next v2 10/10] net: fs_enet: Use cpm_muram_xxx() functions instead of cpm_dpxxx() macros Christophe Leroy
2023-08-06 15:37 ` Simon Horman
2023-08-06 15:37 ` [PATCH net-next v2 00/10] net: fs_enet: Driver cleanup Simon Horman
2023-08-08 22: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=169153262641.13746.13289621238747032969.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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).