From: Jakub Kicinski <kuba@kernel.org>
To: Alexandra Winter <wintera@linux.ibm.com>
Cc: "Yunseong Kim" <yskelg@gmail.com>,
"Markus Elfring" <Markus.Elfring@web.de>,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Bornträger" <borntraeger@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Sven Schnelle" <svens@linux.ibm.com>,
"Thorsten Winkler" <twinkler@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
MichelleJin <shjy180909@gmail.com>
Subject: Re: [PATCH] s390/netiucv: handle memory allocation failure in conn_action_start()
Date: Tue, 25 Jun 2024 08:08:57 -0700 [thread overview]
Message-ID: <20240625080857.46653437@kernel.org> (raw)
In-Reply-To: <6a4b95aa-f3d1-4da1-9017-976420af988b@linux.ibm.com>
On Tue, 25 Jun 2024 11:08:49 +0200 Alexandra Winter wrote:
> s390/netiucv is more or less in maintenance mode and we are not aware of any users.
> The enterprise distros do not provide this module. Other iucv modules are more popular.
> But afaiu we cannot remove the source code, unless we can prove that nobody is using it.
> (Community advice is welcome).
If you have strong reason to believe this driver is unused, and can't
find any proof otherwise - let's remove it. We can always "revert it
back in", if needed. We have done it in the past.
prev parent reply other threads:[~2024-06-25 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 13:11 [PATCH] s390/netiucv: handle memory allocation failure in conn_action_start() yskelg
2024-06-23 14:27 ` Markus Elfring
2024-06-24 18:00 ` Yunseong Kim
2024-06-25 9:08 ` Alexandra Winter
2024-06-25 15:08 ` Jakub Kicinski [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=20240625080857.46653437@kernel.org \
--to=kuba@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shjy180909@gmail.com \
--cc=svens@linux.ibm.com \
--cc=twinkler@linux.ibm.com \
--cc=wintera@linux.ibm.com \
--cc=yskelg@gmail.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).