From: Florian Fainelli <f.fainelli@gmail.com>
To: Yuiko Oshino <yuiko.oshino@microchip.com>,
andrew@lunn.ch, davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net] net: phy: micrel: add Microchip KSZ9131 inital driver
Date: Wed, 26 Sep 2018 11:34:56 -0700 [thread overview]
Message-ID: <3b1aab2e-ed4c-dc36-4035-ce817df467e9@gmail.com> (raw)
In-Reply-To: <1537986141-22832-1-git-send-email-yuiko.oshino@microchip.com>
On 09/26/2018 11:22 AM, Yuiko Oshino wrote:
> Add support for Microchip Technology KSZ9131 10/100/1000 Ethernet phy
>
> Signed-off-by: Yuiko Oshino <yuiko.oshino@microchip.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Same as the previous patch, targeting the "net" tree is not appropriate
here.
Since the two patches are obviously linked, you might consider adding a
cover letter to introduce them.
Thanks!
--
Florian
prev parent reply other threads:[~2018-09-26 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 18:22 [PATCH net] net: phy: micrel: add Microchip KSZ9131 inital driver Yuiko Oshino
2018-09-26 18:34 ` Florian Fainelli [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=3b1aab2e-ed4c-dc36-4035-ce817df467e9@gmail.com \
--to=f.fainelli@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yuiko.oshino@microchip.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