| commit | fb3dc5b8adef1b05e2ca2a48db9fcf1a35ae9a1e | [log] [tgz] |
|---|---|---|
| author | David S. Miller <davem@davemloft.net> | Tue Dec 20 13:50:51 2016 -0500 |
| committer | David S. Miller <davem@davemloft.net> | Tue Dec 20 13:50:51 2016 -0500 |
| tree | aa26f239778a5429318bb40b26ac3479fa5e45e5 | |
| parent | 0a28cfd51e17f4f0a056bcf66bfbe492c3b99f38 [diff] | |
| parent | 308d3165d8b2b98d3dc3d97d6662062735daea67 [diff] |
Merge branch 'phy-broken-modes' Jerome Brunet says: ==================== phy: Fix integration of eee-broken-modes The purpose of this series is to fix the integration of the ethernet phy property "eee-broken-modes" [0] The v3 of this series has been merged, missing a fix (error reported by kbuild robot) available in the v4 [1] More importantly, Florian opposed adding a DT property mapping a device register this directly [2]. The concern was that the property could be abused to implement platform configuration policy. After discussing it, I think we agreed that such information about the HW (defect) should appear in the platform DT. However, the preferred way is to add a boolean property for each EEE broken mode. [0]: http://lkml.kernel.org/r/1480326409-25419-1-git-send-email-jbrunet@baylibre.com [1]: http://lkml.kernel.org/r/1480348229-25672-1-git-send-email-jbrunet@baylibre.com [2]: http://lkml.kernel.org/r/e14a3b0c-dc34-be14-48b3-518a0ad0c080@gmail.com ==================== Signed-off-by: David S. Miller <davem@davemloft.net>