public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Ursula Braun <ubraun@linux.vnet.ibm.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
	schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
	ubraun@linux.vnet.ibm.com
Subject: [PATCH net-next 0/1] s390/qeth: remove legacy SNA-support
Date: Tue, 17 Jan 2017 13:39:50 +0100	[thread overview]
Message-ID: <20170117123951.88480-1-ubraun@linux.vnet.ibm.com> (raw)

Dave,

this is the qeth patch provided last week, you have not been happy with,
because you do not want to unilaterally remove support for a chipset.
I understand that, but I am not sure, if the stopped chip support of
vendors is considered to be something equivalent to the removal of
OSN support for s390. At least your arguments tell me that my original
patch description has been misleading.

OSN mode deals with the legacy IBM Systems Network Architecture
(SNA) protocol. Since s390 mainframes ceased to use the SNA protocol
and OSN mode reached its end of life, we do not want to keep code
just needed for legacy IBM SNA traffic in the kernel. Isn't such a
decision comparable for instance to the removal of Token Ring support
in 2012?

Thus am resending the qeth-patch one more time with a different
patch description.

Kind regards, Ursula

Ursula Braun (1):
  s390/qeth: remove legacy SNA-support

 drivers/s390/net/qeth_core.h      |  28 ----
 drivers/s390/net/qeth_core_main.c |  53 ++------
 drivers/s390/net/qeth_core_mpc.c  |   3 -
 drivers/s390/net/qeth_core_mpc.h  |  10 +-
 drivers/s390/net/qeth_core_sys.c  |  17 ---
 drivers/s390/net/qeth_l2_main.c   | 267 +++++++-------------------------------
 6 files changed, 56 insertions(+), 322 deletions(-)

-- 
2.8.4

             reply	other threads:[~2017-01-17 12:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 12:39 Ursula Braun [this message]
2017-01-17 12:39 ` [PATCH net-next 1/1] s390/qeth: remove legacy SNA-support Ursula Braun
2017-01-17 15:26   ` David Miller

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=20170117123951.88480-1-ubraun@linux.vnet.ibm.com \
    --to=ubraun@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=schwidefsky@de.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