[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d4d4837e-bea0-4303-0f66-6433e21c4be8@gmail.com>
Date: Sat, 23 Nov 2019 12:30:36 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>,
Russell King - ARM Linux admin <linux@...linux.org.uk>
Cc: David Miller <davem@...emloft.net>, andrew@...n.ch,
nbd@...nwrt.org, radhey.shyam.pandey@...inx.com,
alexandre.torgue@...com, netdev@...r.kernel.org,
sean.wang@...iatek.com, linux-stm32@...md-mailman.stormreply.com,
vivien.didelot@...il.com, michal.simek@...inx.com,
joabreu@...opsys.com, linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, thomas.petazzoni@...tlin.com,
john@...ozen.org, matthias.bgg@...il.com, peppe.cavallaro@...com,
Mark-MC.Lee@...iatek.com, mcoquelin.stm32@...il.com,
hkallweit1@...il.com
Subject: Re: [CFT PATCH net-next v2] net: phylink: rename mac_link_state() op
to mac_pcs_get_state()
On 11/23/2019 10:38 AM, Jakub Kicinski wrote:
> On Fri, 22 Nov 2019 09:21:37 +0000, Russell King - ARM Linux admin
> wrote:
>> On Thu, Nov 21, 2019 at 07:36:44PM -0800, Florian Fainelli wrote:
>>> Russell, which of this patch or: http://patchwork.ozlabs.org/patch/1197425/
>>>
>>> would you consider worthy of merging?
>>
>> Let's go with v2 for now - it gets the rename done with less risk that
>> there'll be a problem. I can always do the remainder in a separate
>> patch after the merge window as a separate patch.
>
> Florian, I assume you asked because you wanted to do some testing?
> Please let me know if you need more time, otherwise I'll apply this
> later today.
Please go ahead, if there are issues we can always follow-up. Thanks.
--
Florian
Powered by blists - more mailing lists