From: Julian Wiedmann <jwi@linux.vnet.ibm.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Ursula Braun <ubraun@linux.vnet.ibm.com>
Subject: [stable] s390/qeth: stable candidates
Date: Fri, 1 Dec 2017 10:22:37 +0100 [thread overview]
Message-ID: <b3926cd0-cb9d-76f5-587d-98d069c93cb3@linux.vnet.ibm.com> (raw)
(+cc netdev)
Hi Dave,
I scanned over some recent qeth fixes (see below), could you please
pass these on to stable?
Much obliged,
Julian
83cf79a2fec3 s390/qeth: fix early exit from error path
Fixes: 5f78e29ceebf ("qeth: optimize IP handling in rx_mode callback")
For 4.8+
2aa4867198c2 s390/qeth: translate SETVLAN/DELVLAN errors
For 3.19+
4b764d1de395 s390/qeth: don't convert return code twice
Fixes: efbbc1d56774 ("qeth: clean up error handling")
For 3.19+
ec2c6726322f s390/qeth: fix L3 next-hop in xmit qeth hdr
Fixes: 87e7597b5a3f ("qeth: Move away from using neighbour entries in qeth_l3_fill_header()")
For 3.4+
c7258d8637be qeth: fix rx checksum offload handling
Fixes: c8f44affb724 ("net: introduce and use netdev_features_t for device features sets")
For 3.3+
903e48531e8b qeth: check not more than 16 SBALEs on the completion queue
Fixes: 0da9581ddb0f ("qeth: exploit asynchronous delivery of storage blocks")
For 3.2+
acd9776b5c45 s390/qeth: no ETH header for outbound AF_IUCV
Fixes: b333293058aa ("qeth: add support for af_iucv HiperSockets transport)
For 3.2+
dadc08c7e019 s390/qeth: Allow reading hsuid in state DOWN
Fixes: b333293058aa ("qeth: add support for af_iucv HiperSockets transport)
For 3.2+
next reply other threads:[~2017-12-01 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 9:22 Julian Wiedmann [this message]
2017-12-03 2:40 ` [stable] s390/qeth: stable candidates 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=b3926cd0-cb9d-76f5-587d-98d069c93cb3@linux.vnet.ibm.com \
--to=jwi@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ubraun@linux.vnet.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).