From: Andrew Lunn <andrew@lunn.ch>
To: "Onnasch, Alexander (EXT)" <Alexander.Onnasch@landisgyr.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PATCH net : Micrel KSZ8061 PHY link failure after cable connect
Date: Wed, 21 Nov 2018 15:09:55 +0100 [thread overview]
Message-ID: <20181121140955.GA32314@lunn.ch> (raw)
In-Reply-To: <1542805518-10707-1-git-send-email-alexander.onnasch@landisgyr.com>
On Wed, Nov 21, 2018 at 01:05:32PM +0000, Onnasch, Alexander (EXT) wrote:
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> For tree: git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
Hi Alexander
The Reviewed-by: Should go after the Signed-of-by:
And you indicate the tree in the subject line:
[PATCH v2 net] phy: Micrel KSZ8061: link failure after cable connect
Andrew
prev parent reply other threads:[~2018-11-21 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 13:05 PATCH net : Micrel KSZ8061 PHY link failure after cable connect Onnasch, Alexander (EXT)
2018-11-21 14:09 ` Andrew Lunn [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=20181121140955.GA32314@lunn.ch \
--to=andrew@lunn.ch \
--cc=Alexander.Onnasch@landisgyr.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).