From: patchwork-bot+netdevbpf@kernel•org
To: Martin Habets <habetsm.xilinx@gmail•com>
Cc: kuba@kernel•org, edumazet@google•com, pabeni@redhat•com,
davem@davemloft•net, netdev@vger•kernel.org,
ecree.xilinx@gmail•com
Subject: Re: [PATCH net-next v4 00/11]: Move Siena into a separate subdirectory
Date: Wed, 11 May 2022 00:50:15 +0000 [thread overview]
Message-ID: <165223021503.12317.6054987873920924755.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <165211018297.5289.9658523545298485394.stgit@palantir17.mph.net>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Mon, 09 May 2022 16:31:06 +0100 you wrote:
> The Siena NICs (SFN5000 and SFN6000 series) went EOL in November 2021.
> Most of these adapters have been remove from our test labs, and testing
> has been reduced to a minimum.
>
> This patch series creates a separate kernel module for the Siena architecture,
> analogous to what was done for Falcon some years ago.
> This reduces our maintenance for the sfc.ko module, and allows us to
> enhance the EF10 and EF100 drivers without the risk of breaking Siena NICs.
>
> [...]
Here is the summary with links:
- [net-next,v4,01/11] sfc: Move Siena specific files
(no matching commit)
- [net-next,v4,02/11] sfc: Copy shared files needed for Siena (part 1)
(no matching commit)
- [net-next,v4,03/11] sfc: Copy shared files needed for Siena (part 2)
(no matching commit)
- [net-next,v4,04/11] sfc/siena: Remove build references to missing functionality
https://git.kernel.org/netdev/net-next/c/956f2d86cb37
- [net-next,v4,05/11] sfc/siena: Rename functions in efx headers to avoid conflicts with sfc
https://git.kernel.org/netdev/net-next/c/71ad88f66125
- [net-next,v4,06/11] sfc/siena: Rename RX/TX functions to avoid conflicts with sfc
https://git.kernel.org/netdev/net-next/c/7f9e4b2a61ba
- [net-next,v4,07/11] sfc/siena: Rename peripheral functions to avoid conflicts with sfc
https://git.kernel.org/netdev/net-next/c/95e96f7788d0
- [net-next,v4,08/11] sfc/siena: Rename functions in mcdi headers to avoid conflicts with sfc
https://git.kernel.org/netdev/net-next/c/4d49e5cd4b09
- [net-next,v4,09/11] sfc/siena: Rename functions in nic_common.h to avoid conflicts with sfc
https://git.kernel.org/netdev/net-next/c/c8443b698238
- [net-next,v4,10/11] sfc/siena: Inline functions in sriov.h to avoid conflicts with sfc
https://git.kernel.org/netdev/net-next/c/782f7130849f
- [net-next,v4,11/11] sfc: Add a basic Siena module
https://git.kernel.org/netdev/net-next/c/c5a13c319e10
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-05-11 0:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 15:31 [PATCH net-next v4 00/11]: Move Siena into a separate subdirectory Martin Habets
2022-05-09 15:31 ` [PATCH net-next v4 01/11] sfc: Move Siena specific files Martin Habets
2022-05-09 15:31 ` [PATCH net-next v4 02/11] sfc: Copy shared files needed for Siena (part 1) Martin Habets
2022-05-09 15:31 ` [PATCH net-next v4 03/11] sfc: Copy shared files needed for Siena (part 2) Martin Habets
2022-05-09 15:31 ` [PATCH net-next v4 04/11] sfc/siena: Remove build references to missing functionality Martin Habets
2022-05-09 15:32 ` [PATCH net-next v4 05/11] sfc/siena: Rename functions in efx headers to avoid conflicts with sfc Martin Habets
2022-05-09 15:32 ` [PATCH net-next v4 06/11] sfc/siena: Rename RX/TX functions " Martin Habets
2022-05-09 15:32 ` [PATCH net-next v4 07/11] sfc/siena: Rename peripheral " Martin Habets
2022-05-09 15:32 ` [PATCH net-next v4 08/11] sfc/siena: Rename functions in mcdi headers " Martin Habets
2022-05-09 15:32 ` [PATCH net-next v4 09/11] sfc/siena: Rename functions in nic_common.h " Martin Habets
2022-05-09 15:33 ` [PATCH net-next v4 10/11] sfc/siena: Inline functions in sriov.h " Martin Habets
2022-05-09 15:33 ` [PATCH net-next v4 11/11] sfc: Add a basic Siena module Martin Habets
2022-05-10 0:30 ` [PATCH net-next v4 00/11]: Move Siena into a separate subdirectory patchwork-bot+netdevbpf
2022-05-10 8:06 ` Martin Habets
2022-05-11 0: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=165223021503.12317.6054987873920924755.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=ecree.xilinx@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=habetsm.xilinx@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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