From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Thomas Bogendoerfer <tbogendoerfer@suse.de>,
antoine.tenart@bootlin.com, maxime.chevallier@bootlin.com,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: mvpp2: fix condition for setting up link interrupt
Date: Thu, 24 Jan 2019 16:07:41 +0000 [thread overview]
Message-ID: <20190124160741.jady3r2e4dme7c4m@e5254000004ec.dyn.armlinux.org.uk> (raw)
In-Reply-To: <20190124155137.GD482@lunn.ch>
On Thu, Jan 24, 2019 at 04:51:37PM +0100, Andrew Lunn wrote:
> On Thu, Jan 24, 2019 at 02:18:03PM +0100, Thomas Bogendoerfer wrote:
> > Set up link interrupt if connection is handled by phylink otherwise
> > link state change detection for in-band-status doesn't work.
>
> Hi Thomas
>
> Please ensure the maintainers of the driver are at least on Cc:
... and other interested parties!
> Thanks
> Andrew
>
> >
> > Fixes: 4bb043262878 ("net: mvpp2: phylink support")
> > Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
> > ---
> > drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c b/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
> > index 16066c2d5b3a..0fbfe1945a69 100644
> > --- a/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
> > +++ b/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
> > @@ -3405,7 +3405,7 @@ static int mvpp2_open(struct net_device *dev)
> > valid = true;
> > }
> >
> > - if (priv->hw_version == MVPP22 && port->link_irq && !port->phylink) {
> > + if (priv->hw_version == MVPP22 && port->link_irq && port->phylink) {
> > err = request_irq(port->link_irq, mvpp2_link_status_isr, 0,
> > dev->name, port);
> > if (err) {
This still looks fishy to me. mvpp2_link_status_isr() has handling in
it that is safe to be called for non-phylink cases, so presumably the
right fix is to drop the "&& !port->phylink" completely?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-01-24 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 13:18 Thomas Bogendoerfer
2019-01-24 15:51 ` Andrew Lunn
2019-01-24 16:07 ` Russell King - ARM Linux admin [this message]
2019-01-24 16:15 ` Andrew Lunn
2019-01-24 16:26 ` Russell King - ARM Linux admin
2019-01-24 16:17 ` Thomas Bogendoerfer
2019-01-25 8:37 ` Antoine Tenart
2019-01-25 15:18 ` Thomas Bogendoerfer
2019-12-08 16:42 ` Russell King - ARM Linux admin
2019-12-08 17:14 ` Willy Tarreau
2019-12-10 14:53 ` Antoine Tenart
2019-12-10 14:58 ` Russell King - ARM Linux admin
2019-01-24 16:15 ` Thomas Bogendoerfer
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=20190124160741.jady3r2e4dme7c4m@e5254000004ec.dyn.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=tbogendoerfer@suse.de \
/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
all inboxes | Powered by JetHome®