From: Andrew Lunn <andrew@lunn.ch>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
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 17:15:35 +0100 [thread overview]
Message-ID: <20190124161535.GH482@lunn.ch> (raw)
In-Reply-To: <20190124160741.jady3r2e4dme7c4m@e5254000004ec.dyn.armlinux.org.uk>
On Thu, Jan 24, 2019 at 04:07:41PM +0000, Russell King - ARM Linux admin wrote:
> 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!
Hi Russell
get_maintainer.pl does not list you, so it can be hard to know who
those other interested parties are. I have local knowledge, so added
you :-)
Andrew
next prev parent reply other threads:[~2019-01-24 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 13:18 [PATCH net] net: mvpp2: fix condition for setting up link interrupt Thomas Bogendoerfer
2019-01-24 15:51 ` Andrew Lunn
2019-01-24 16:07 ` Russell King - ARM Linux admin
2019-01-24 16:15 ` Andrew Lunn [this message]
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=20190124161535.GH482@lunn.ch \
--to=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).