public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Dongpo Li <lidongpo@hisilicon.com>
Cc: f.fainelli@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
	frowand.list@gmail.com, davem@davemloft.net, andrew@lunn.ch,
	xuejiancheng@hisilicon.com, benjamin.chenhao@hisilicon.com,
	howell.yang@hisilicon.com, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/3] Add Hisilicon MDIO bus driver and FEMAC driver
Date: Fri, 15 Jul 2016 10:41:07 +0200	[thread overview]
Message-ID: <20917223.X0KrqBAbxT@wuerfel> (raw)
In-Reply-To: <1468571195-59763-1-git-send-email-lidongpo@hisilicon.com>

On Friday, July 15, 2016 4:26:32 PM CEST Dongpo Li wrote:
> This patch set adds a Hisilicon MDIO bus driver and
> a Fast Ethernet MAC(FEMAC) driver.
> We also abstract a general interface "of_phy_get_and_connect"
> for PHY connect. User will have no bother with getting
> "phy-mode" and "phy-handle" any more.
> 
> Changes in v1:
> - Pass private data structure instead of struct mii_bus
>   in MDIO read and write operation.
> - Return the error which devm_clk_get() gives when MDIO probe.
> - Leave the clock unprepared and disabled on error when MDIO probe.
> - Abstract a general interface "of_phy_get_and_connect" for PHY connect.
> - Remove the "_reset" suffixes in "reset-names" property.
> - Enable tx per-packet interrupt when tx fifo full.
> - Remove pointless compatible and add SoC specific compatible.
> - Declare only one clock in MAC dts documentation.
> - Add standard unit suffixes for "phy-reset-delays".
> - Use a smaller NAPI poll weight 16 for our Fast Ethernet MAC.
> - Use phy_ethtool_{get|set}_link_ksettings for ethtool ops.
> - Use phydev from struct net_device in MAC driver.
> 

Looks all good to me now,

Reviewed-by: Arnd Bergmann <arnd@arndb.de>

One comment on the submission format: we normally count the initial
submission as "v1", so after [PATCH 0/3], the following version is
[PATCH v2 0/3], not [PATCH v1 0/3].

No need to re-send for this now, and if you end up having to make
other changes, just continue with "v2" for this driver, just follow
the normal scheme if you send another driver.

	Arnd

  parent reply	other threads:[~2016-07-15  8:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15  8:26 [PATCH v1 0/3] Add Hisilicon MDIO bus driver and FEMAC driver Dongpo Li
2016-07-15  8:26 ` [PATCH v1 1/3] net: Add MDIO bus driver for the Hisilicon FEMAC Dongpo Li
2016-07-15 14:42   ` Andrew Lunn
2016-07-15  8:26 ` [PATCH v1 2/3] of_mdio: Abstract a general interface for phy connect Dongpo Li
2016-07-15  8:26 ` [PATCH v1 3/3] net: hisilicon: Add Fast Ethernet MAC driver Dongpo Li
2016-07-15  8:41 ` Arnd Bergmann [this message]
2016-07-15  9:02   ` [PATCH v1 0/3] Add Hisilicon MDIO bus driver and FEMAC driver Dongpo Li
2016-07-17  4:44 ` 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=20917223.X0KrqBAbxT@wuerfel \
    --to=arnd@arndb.de \
    --cc=andrew@lunn.ch \
    --cc=benjamin.chenhao@hisilicon.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=frowand.list@gmail.com \
    --cc=howell.yang@hisilicon.com \
    --cc=lidongpo@hisilicon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=xuejiancheng@hisilicon.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