[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <be9bb84c-6c0c-3106-ccbb-99b15ad5b30e@gmail.com>
Date: Mon, 20 May 2019 10:21:26 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Marek Vasut <marex@...x.de>, Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, Guenter Roeck <linux@...ck-us.net>,
Heiner Kallweit <hkallweit1@...il.com>,
Jean Delvare <jdelvare@...e.com>, linux-hwmon@...r.kernel.org
Subject: Re: [PATCH V5] net: phy: tja11xx: Add TJA11xx PHY driver
On May 18, 2019 9:50:48 AM PDT, Marek Vasut <marex@...x.de> wrote:
>On 5/18/19 4:14 PM, Andrew Lunn wrote:
>> On Sat, May 18, 2019 at 01:51:23AM +0200, Marek Vasut wrote:
>>> Add driver for the NXP TJA1100 and TJA1101 PHYs. These PHYs are
>special
>>> BroadRReach 100BaseT1 PHYs used in automotive.
>>
>> Hi Marek
>
>Hello Andrew,
>
>>> + }, {
>>> + PHY_ID_MATCH_MODEL(PHY_ID_TJA1101),
>>> + .name = "NXP TJA1101",
>>> + .features = PHY_BASIC_T1_FEATURES,
>>
>> One thing i would like to do before this patch goes in is define
>> ETHTOOL_LINK_MODE_100baseT1_Full_BIT in ethtool.h, and use it here.
>> We could not do it earlier because were ran out of bits. But with
>> PHYLIB now using bitmaps, rather than u32, we can.
>>
>> Once net-next reopens i will submit a patch adding it.
>
>I can understand blocking patches from being applied if they have
>review
>problems or need to be updated on some existing or even posted feature.
>But blocking a patch because some future yet-to-be-developed patch is a
>bit odd.
>
The net-next tree is currently closed which means there is ample time
for you and Andrew to work offline and have you submit both Andrew's
cleanup patches as well as this very one as a patch series when net-next
opens back up giving both of you your own cookies. Once submitted it
won't take weeks to get merged more like hours given David's typical
review and patch acceptance time.
--
Florian
Powered by blists - more mailing lists