netdev - [PATCH 0/7] net: of

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 5 Dec 2013 14:52:09 -0800
From:	Florian Fainelli <florian@...nwrt.org>
To:	<netdev@...r.kernel.org>
CC:	<davem@...emloft.net>, <grant.likely@...aro.org>,
	<devicetree@...r.kernel.org>, <abrodkin@...opsys.com>,
	<rob.herring@...xeda.com>, <mark.rutland@....com>,
	<sebastian.hesselbarth@...il.com>,
	Florian Fainelli <florian@...nwrt.org>
Subject: [PATCH 0/7] net: of_mdio improvements

Hi all,

This patchset contains a few improvements to the MDIO device tree parsing
code such as refactoring and parsing the "max-speed" property which is
defined in the ePAPR specification.

Thanks!

Florian Fainelli (7):
  net: of_mdio: factor PHY registration from of_mdiobus_register
  net: of_mdio: use PHY_MAX_ADDR constant
  net: of_mdio: do not overwrite PHY interrupt configuration
  net: phy: breakdown PHY_*_FEATURES defines
  net: of_mdio: parse "max-speed" property to set PHY supported features
  arc_emac: remove custom "max-speed" parsing code
  Documentation: update Ethernet PHY devices binding with 'max-speed'

 Documentation/devicetree/bindings/net/phy.txt |   1 +
 drivers/net/ethernet/arc/emac.h               |   2 -
 drivers/net/ethernet/arc/emac_main.c          |  20 +---
 drivers/of/of_mdio.c                          | 135 ++++++++++++++------------
 include/linux/phy.h                           |  23 +++--
 5 files changed, 89 insertions(+), 92 deletions(-)

-- 
1.8.3.2

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html