From: Florian Fainelli <f.fainelli@gmail.com>
To: Yuiko Oshino <yuiko.oshino@microchip.com>,
davem@davemloft.net, robh+dt@kernel.org,
devicetree@vger.kernel.org, andrew@lunn.ch
Cc: linux-kernel@vger.kernel.org, mark.rutland@arm.com,
m.felsch@pengutronix.de, Markus.Niebel@tqs.de,
netdev@vger.kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v2 net-next 0/2] Add support for Microchip Technology KSZ9131 10/100/1000 Ethernet PHY
Date: Thu, 27 Sep 2018 12:28:31 -0700 [thread overview]
Message-ID: <7c84dfed-6864-7b25-38d1-9bed1cfea0bc@gmail.com> (raw)
In-Reply-To: <1538079344-6152-1-git-send-email-yuiko.oshino@microchip.com>
On 09/27/2018 01:15 PM, Yuiko Oshino wrote:
> This is the initial driver for Microchip KSZ9131 10/100/1000 Ethernet PHY
>
> v2:
> - Creating a series from two related patches.
When people give you Acked-by or Reviewed-by tags in prior versions, it
is usually a good practice to add them to your next version of the
patch submission. Also, your patches 1 and 2 did not show up as as reply
to this cover letter, while they should, please fix this if you ever
need to submit new patches in the future.
Thank you!
>
> Yuiko Oshino (2):
> net: phy: micrel: add Microchip KSZ9131 inital driver
> dt-bindings: net: add support for Microchip KSZ9131 Ethernet PHY
>
> .../devicetree/bindings/net/micrel-ksz90x1.txt | 29 +++++++++++++++++++-
> drivers/net/phy/micrel.c | 32 ++++++++++++++++++++--
> include/linux/micrel_phy.h | 1 +
> 3 files changed, 58 insertions(+), 4 deletions(-)
>
--
Florian
next prev parent reply other threads:[~2018-09-27 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 20:15 [PATCH v2 net-next 0/2] Add support for Microchip Technology KSZ9131 10/100/1000 Ethernet PHY Yuiko Oshino
2018-09-27 19:28 ` Florian Fainelli [this message]
2018-09-28 14:51 ` Yuiko.Oshino
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=7c84dfed-6864-7b25-38d1-9bed1cfea0bc@gmail.com \
--to=f.fainelli@gmail.com \
--cc=Markus.Niebel@tqs.de \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).