From: David Miller <davem@davemloft.net>
To: jwi@linux.ibm.com
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
raspl@linux.ibm.com, ubraun@linux.ibm.com
Subject: Re: [PATCH net 0/6] s390/qeth: fixes 2018-11-02
Date: Sat, 03 Nov 2018 10:44:23 -0700 (PDT) [thread overview]
Message-ID: <20181103.104423.164937572040750291.davem@davemloft.net> (raw)
In-Reply-To: <20181102180413.53020-1-jwi@linux.ibm.com>
From: Julian Wiedmann <jwi@linux.ibm.com>
Date: Fri, 2 Nov 2018 19:04:07 +0100
> please apply one round of qeth fixes for -net.
>
> Patch 1 is rather large and removes a use-after-free hazard from many of our
> debug trace entries.
> Patch 2 is yet another fix-up for the L3 subdriver's new IP address management
> code.
> Patch 3 and 4 resolve some fallout from the recent changes wrt how/when qeth
> allocates its net_device.
> Patch 5 makes sure we don't set reserved bits when building HW commands from
> user-provided data.
> And finally, patch 6 allows ethtool to play nice with new HW.
Series applied.
prev parent reply other threads:[~2018-11-04 2:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 18:04 [PATCH net 0/6] s390/qeth: fixes 2018-11-02 Julian Wiedmann
2018-11-02 18:04 ` [PATCH net 1/6] s390/qeth: sanitize strings in debug messages Julian Wiedmann
2018-11-02 18:04 ` [PATCH net 2/6] s390/qeth: fix HiperSockets sniffer Julian Wiedmann
2018-11-02 18:04 ` [PATCH net 3/6] s390/qeth: unregister netdevice only when registered Julian Wiedmann
2018-11-02 18:04 ` [PATCH net 4/6] s390/qeth: fix initial operstate Julian Wiedmann
2018-11-02 18:04 ` [PATCH net 5/6] s390/qeth: sanitize ARP requests Julian Wiedmann
2018-11-02 18:04 ` [PATCH net 6/6] s390/qeth: report 25Gbit link speed Julian Wiedmann
2018-11-03 17:44 ` David Miller [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=20181103.104423.164937572040750291.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=jwi@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@linux.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=ubraun@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).