Re: [net-next v2 0/8] drivers/s390/net/ism: Add generalized interface - patchwork-bot+netdevbpf

From: patchwork-bot+netdevbpf@kernel.org
To: Jan Karcher <jaka@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-s390@vger.kernel.org, hca@linux.ibm.com,
	wintera@linux.ibm.com, wenjia@linux.ibm.com,
	twinkler@linux.ibm.com, raspl@linux.ibm.com,
	kgraul@linux.ibm.com, niho@linux.ibm.com, pasic@linux.ibm.com,
	tonylu@linux.alibaba.com, guwen@linux.alibaba.com
Subject: Re: [net-next v2 0/8] drivers/s390/net/ism: Add generalized interface
Date: Wed, 25 Jan 2023 10:00:18 +0000	[thread overview]
Message-ID: <167464081878.8627.16367625565624680378.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230123181752.1068-1-jaka@linux.ibm.com>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon, 23 Jan 2023 19:17:44 +0100 you wrote:
> Previously, there was no clean separation between SMC-D code and the ISM
> device driver.This patch series addresses the situation to make ISM available
> for uses outside of SMC-D.
> In detail: SMC-D offers an interface via struct smcd_ops, which only the
> ISM module implements so far. However, there is no real separation between
> the smcd and ism modules, which starts right with the ISM device
> initialization, which calls directly into the SMC-D code.
> This patch series introduces a new API in the ISM module, which allows
> registration of arbitrary clients via include/linux/ism.h: struct ism_client.
> Furthermore, it introduces a "pure" struct ism_dev (i.e. getting rid of
> dependencies on SMC-D in the device structure), and adds a number of API
> calls for data transfers via ISM (see ism_register_dmb() & friends).
> Still, the ISM module implements the SMC-D API, and therefore has a number
> of internal helper functions for that matter.
> Note that the ISM API is consciously kept thin for now (as compared to the
> SMC-D API calls), as a number of API calls are only used with SMC-D and
> hardly have any meaningful usage beyond SMC-D, e.g. the VLAN-related calls.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/8] net/smc: Terminate connections prior to device removal
    https://git.kernel.org/netdev/net-next/c/c40bff4132e5
  - [net-next,v2,2/8] net/ism: Add missing calls to disable bus-mastering
    https://git.kernel.org/netdev/net-next/c/462502ff9acb
  - [net-next,v2,3/8] s390/ism: Introduce struct ism_dmb
    https://git.kernel.org/netdev/net-next/c/1baedb13f1d5
  - [net-next,v2,4/8] net/ism: Add new API for client registration
    https://git.kernel.org/netdev/net-next/c/89e7d2ba61b7
  - [net-next,v2,5/8] net/smc: Register SMC-D as ISM client
    https://git.kernel.org/netdev/net-next/c/8747716f3942
  - [net-next,v2,6/8] net/smc: Separate SMC-D and ISM APIs
    https://git.kernel.org/netdev/net-next/c/9de4df7b6be1
  - [net-next,v2,7/8] s390/ism: Consolidate SMC-D-related code
    https://git.kernel.org/netdev/net-next/c/820f21009f1b
  - [net-next,v2,8/8] net/smc: De-tangle ism and smc device initialization
    https://git.kernel.org/netdev/net-next/c/8c81ba20349d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html