From: Shannon Nelson <shannon.nelson@oracle.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: sparclinux@vger.kernel.org, Shannon Nelson <shannon.nelson@oracle.com>
Subject: [PATCH net-next 0/2] ldmvsw: port removal stability
Date: Mon, 15 May 2017 10:51:06 -0700 [thread overview]
Message-ID: <1494870668-65047-1-git-send-email-shannon.nelson@oracle.com> (raw)
Under heavy reboot stress testing we found a couple of timing issues
when removing the device that could cause the kernel great heartburn,
addressed by these two patches.
Shannon Nelson (1):
ldmvsw: stop the clean timer at beginning of remove
Thomas Tai (1):
ldmvsw: unregistering netdev before disable hardware
drivers/net/ethernet/sun/ldmvsw.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2017-05-15 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 17:51 Shannon Nelson [this message]
2017-05-15 17:51 ` [PATCH net-next 1/2] ldmvsw: unregistering netdev before disable hardware Shannon Nelson
2017-05-15 17:51 ` [PATCH net-next 2/2] ldmvsw: stop the clean timer at beginning of remove Shannon Nelson
2017-05-15 19:36 ` [PATCH net-next 0/2] ldmvsw: port removal stability 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=1494870668-65047-1-git-send-email-shannon.nelson@oracle.com \
--to=shannon.nelson@oracle.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/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).