[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250220172410.025b96d6@kernel.org>
Date: Thu, 20 Feb 2025 17:24:10 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Meghana Malladi <m-malladi@...com>
Cc: Jacob Keller <jacob.e.keller@...el.com>, <lokeshvutla@...com>,
<vigneshr@...com>, <javier.carrasco.cruz@...il.com>,
<diogo.ivo@...mens.com>, <horms@...nel.org>, <pabeni@...hat.com>,
<edumazet@...gle.com>, <davem@...emloft.net>, <andrew+netdev@...n.ch>,
<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <srk@...com>, Roger Quadros
<rogerq@...nel.org>, <danishanwar@...com>
Subject: Re: [PATCH net v2 0/2] Fixes for perout configuration in IEP driver
On Wed, 19 Feb 2025 15:37:16 -0800 Jacob Keller wrote:
> On 2/18/2025 10:26 PM, Meghana Malladi wrote:
> > IEP driver supports both pps and perout signal generation using testptp
> > application. Currently the driver is missing to incorporate the perout
> > signal configuration. This series introduces fixes in the driver to
> > configure perout signal based on the arguments passed by the perout
> > request.
> >
>
> This could be interpreted as a feature implementation rather than a fix.
>
> Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
Agreed, ideally we should get a patch for net which rejects
all currently (as in - in Linus's tree) unsupported settings.
That would be a fix.
Then once that's merged add support for the new settings in net-next.
Hope that makes sense?
--
pw-bot: cr
Powered by blists - more mailing lists