From: David Miller <davem@davemloft.net>
To: andrew@lunn.ch
Cc: netdev@vger.kernel.org, vivien.didelot@savoirfairelinux.com
Subject: Re: [PATCH net 0/2] mv88e6xxx error patch fixes
Date: Thu, 07 Dec 2017 13:53:23 -0500 (EST) [thread overview]
Message-ID: <20171207.135323.344412933569991466.davem@davemloft.net> (raw)
In-Reply-To: <1512605157-6765-1-git-send-email-andrew@lunn.ch>
From: Andrew Lunn <andrew@lunn.ch>
Date: Thu, 7 Dec 2017 01:05:55 +0100
> While trying to bring up a new PHY on a board, i exercised the error
> paths a bit, and discovered some bugs. The unwind for interrupt
> handling deadlocks, and the MDIO code hits a BUG() when a registered
> MDIO device is freed without first being unregistered.
Series applied, thanks Andrew.
prev parent reply other threads:[~2017-12-07 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 0:05 [PATCH net 0/2] mv88e6xxx error patch fixes Andrew Lunn
2017-12-07 0:05 ` [PATCH net 1/2] net: dsa: mv88e6xxx: Fix interrupt masking on removal Andrew Lunn
2017-12-07 15:33 ` Vivien Didelot
2017-12-07 0:05 ` [PATCH net 2/2] net: dsa: mv88e6xxx: Unregister MDIO bus on error path Andrew Lunn
2017-12-07 15:33 ` Vivien Didelot
2017-12-07 18:53 ` 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=20171207.135323.344412933569991466.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).