From: Andrew Lunn <andrew@lunn.ch>
To: Yan Markman <ymarkman@marvell.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
"David S. Miller" <davem@davemloft.net>,
Russell King <rmk+kernel@armlinux.org.uk>,
open list <linux-kernel@vger.kernel.org>,
Antoine Tenart <antoine.tenart@bootlin.com>,
Stefan Chulski <stefanc@marvell.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Miquel Raynal <miquel.raynal@free-electrons.com>,
Marcin Wojtas <mw@semihalf.com>,
Yelena Krivosheev <yelena@marvell.com>
Subject: Re: [EXT] [PATCH net-next v2 1/2] net: phy: phylink: Provide PHY interface to mac_link_{up,down}
Date: Thu, 29 Mar 2018 14:57:39 +0200 [thread overview]
Message-ID: <20180329125739.GA3798@lunn.ch> (raw)
In-Reply-To: <843035ef7cfb45a7a02be516b8fcdd49@IL-EXCH01.marvell.com>
On Thu, Mar 29, 2018 at 05:59:02AM +0000, Yan Markman wrote:
> Hi Florian
> Please keep CC Yelena Krivosheev <yelena@marvell.com>
> for changes with drivers/net/ethernet/marvell/mvneta.c
> Thanks
> Yan Markman
> Tel. 05-44732819
Hi Yan
Since you have obviously seen the patches, how about a Reviewed-by, or
a Tested-by.
Andrew
next prev parent reply other threads:[~2018-03-29 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 22:44 [PATCH net-next v2 0/2] phylink: API changes Florian Fainelli
2018-03-28 22:44 ` [PATCH net-next v2 1/2] net: phy: phylink: Provide PHY interface to mac_link_{up,down} Florian Fainelli
2018-03-29 5:59 ` [EXT] " Yan Markman
2018-03-29 12:57 ` Andrew Lunn [this message]
2018-03-28 22:44 ` [PATCH net-next v2 2/2] sfp/phylink: move module EEPROM ethtool access into netdev core ethtool Florian Fainelli
2018-03-29 5:59 ` [EXT] " Yan Markman
2018-03-29 5:58 ` [EXT] [PATCH net-next v2 0/2] phylink: API changes Yan Markman
2018-03-29 7:44 ` Russell King - ARM Linux
2018-03-30 14:11 ` 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=20180329125739.GA3798@lunn.ch \
--to=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=miquel.raynal@free-electrons.com \
--cc=mw@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stefanc@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=yelena@marvell.com \
--cc=ymarkman@marvell.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).