From: patchwork-bot+netdevbpf@kernel.org
To: Alexandra Winter <wintera@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
borntraeger@linux.ibm.com, svens@linux.ibm.com,
twinkler@linux.ibm.com, horms@kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org, nagamani@linux.ibm.com
Subject: Re: [PATCH net-next] s390/net: Remove NETIUCV device driver
Date: Thu, 17 Jul 2025 01:30:18 +0000 [thread overview]
Message-ID: <175271581800.1388574.4454566301754879755.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250715074210.3999296-1-wintera@linux.ibm.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 15 Jul 2025 09:42:10 +0200 you wrote:
> From: Nagamani PV <nagamani@linux.ibm.com>
>
> The netiucv driver creates TCP/IP interfaces over IUCV between Linux
> guests on z/VM and other z/VM entities.
>
> Rationale for removal:
> - NETIUCV connections are only supported for compatibility with
> earlier versions and not to be used for new network setups,
> since at least Linux kernel 4.0.
> - No known active users, use cases, or product dependencies
> - The driver is no longer relevant for z/VM networking;
> preferred methods include:
> * Device pass-through (e.g., OSA, RoCE)
> * z/VM Virtual Switch (VSWITCH)
>
> [...]
Here is the summary with links:
- [net-next] s390/net: Remove NETIUCV device driver
https://git.kernel.org/netdev/net-next/c/727258025b93
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:[~2025-07-17 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 7:42 [PATCH net-next] s390/net: Remove NETIUCV device driver Alexandra Winter
2025-07-15 14:33 ` Simon Horman
2025-07-17 1:30 ` 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=175271581800.1388574.4454566301754879755.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=andrew+netdev@lunn.ch \
--cc=borntraeger@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nagamani@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=svens@linux.ibm.com \
--cc=twinkler@linux.ibm.com \
--cc=wintera@linux.ibm.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).