[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cbb3cca4-6376-a7b5-d10e-4e2d721ce667@oss.nxp.com>
Date: Fri, 8 Sep 2023 09:09:46 +0300
From: "Radu Pirea (OSS)" <radu-nicolae.pirea@....nxp.com>
To: Simon Horman <horms@...nel.org>
Cc: andrew@...n.ch, hkallweit1@...il.com, linux@...linux.org.uk,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, richardcochran@...il.com, sd@...asysnail.net,
sebastian.tobuschat@....com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC net-next v3 6/6] net: phy: nxp-c45-tja11xx: implement
mdo_insert_tx_tag
On 07.09.2023 18:04, Simon Horman wrote:
> On Wed, Sep 06, 2023 at 07:01:34PM +0300, Radu Pirea (NXP OSS) wrote:
>
> Hi Radu,
>
> I hate to be the bearer of bad news, but
> I don't think we can accept new module parameters in Networking code.
No problem. I should have removed the parameter, but I missed the CI
error from RFC v2.
--
Radu P.
Powered by blists - more mailing lists