From: Julian Wiedmann <jwi@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-s390@vger.kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Stefan Raspl <raspl@linux.vnet.ibm.com>,
Ursula Braun <ubraun@linux.vnet.ibm.com>,
Julian Wiedmann <jwi@linux.vnet.ibm.com>
Subject: [PATCH net-next 00/12] s390/net: updates for 4.14
Date: Tue, 15 Aug 2017 17:02:38 +0200 [thread overview]
Message-ID: <20170815150250.67158-1-jwi@linux.vnet.ibm.com> (raw)
Hi Dave,
a mixed bag of minor fixes, cleanups and refactors for net-next. Please apply.
Thanks,
Julian
Julian Wiedmann (9):
s390/qeth: don't access skb after transmission
s390/qeth: remove extra L2 adapterparms query
s390/qeth: remove extra L3 adapterparms query
s390/qeth: simplify fragment type selection
s390/qeth: straighten out fill_buffer() interface
s390/qeth: clean up fill_buffer() offset logic
s390/qeth: make more use of skb API
s390/net: reduce inlining
s390/qeth: extract bridgeport cmd builder
Kittipon Meesompop (3):
s390/qeth: reject multicast rxip addresses
s390/qeth: fix trace-messages for deleting rxip addresses
s390/qeth: fix using of ref counter for rxip addresses
drivers/s390/net/ctcm_main.c | 2 +-
drivers/s390/net/lcs.c | 28 ++++----
drivers/s390/net/netiucv.c | 4 +-
drivers/s390/net/qeth_core.h | 11 ++-
drivers/s390/net/qeth_core_main.c | 147 ++++++++++++++++++--------------------
drivers/s390/net/qeth_core_sys.c | 2 +-
drivers/s390/net/qeth_l2_main.c | 116 +++++++++++-------------------
drivers/s390/net/qeth_l3_main.c | 49 +++++--------
drivers/s390/net/qeth_l3_sys.c | 17 +++++
9 files changed, 169 insertions(+), 207 deletions(-)
--
2.11.2
next reply other threads:[~2017-08-15 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 15:02 Julian Wiedmann [this message]
2017-08-15 15:02 ` [PATCH net-next 01/12] s390/qeth: don't access skb after transmission Julian Wiedmann
2017-08-15 15:02 ` [PATCH net-next 02/12] s390/qeth: remove extra L2 adapterparms query Julian Wiedmann
2017-08-15 15:02 ` [PATCH net-next 03/12] s390/qeth: remove extra L3 " Julian Wiedmann
2017-08-15 15:02 ` [PATCH net-next 04/12] s390/qeth: simplify fragment type selection Julian Wiedmann
2017-08-15 15:02 ` [PATCH net-next 05/12] s390/qeth: straighten out fill_buffer() interface Julian Wiedmann
2017-08-15 15:02 ` [PATCH net-next 06/12] s390/qeth: clean up fill_buffer() offset logic Julian Wiedmann
2017-08-15 15:02 ` [PATCH net-next 07/12] s390/qeth: make more use of skb API Julian Wiedmann
2017-08-15 15:02 ` [PATCH net-next 08/12] s390/net: reduce inlining Julian Wiedmann
2017-08-15 15:02 ` [PATCH net-next 09/12] s390/qeth: extract bridgeport cmd builder Julian Wiedmann
2017-08-15 15:02 ` [PATCH net-next 10/12] s390/qeth: reject multicast rxip addresses Julian Wiedmann
2017-08-15 15:02 ` [PATCH net-next 11/12] s390/qeth: fix trace-messages for deleting " Julian Wiedmann
2017-08-15 15:02 ` [PATCH net-next 12/12] s390/qeth: fix using of ref counter for " Julian Wiedmann
2017-08-15 18:00 ` [PATCH net-next 00/12] s390/net: updates for 4.14 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=20170815150250.67158-1-jwi@linux.vnet.ibm.com \
--to=jwi@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=raspl@linux.vnet.ibm.com \
--cc=schwidefsky@de.ibm.com \
--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).