[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZOBpRmHXndkvFcnA@vergenet.net>
Date: Sat, 19 Aug 2023 09:03:34 +0200
From: Simon Horman <horms@...nel.org>
To: Ruan Jinjie <ruanjinjie@...wei.com>
Cc: horatiu.vultur@...rochip.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, lars.povlsen@...rochip.com,
Steen.Hegelund@...rochip.com, daniel.machon@...rochip.com,
richardcochran@...il.com, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH net-next v2 0/3] net: Update and fix return value check
for vcap_get_rule()
On Fri, Aug 18, 2023 at 01:05:02PM +0800, Ruan Jinjie wrote:
> As Simon Horman suggests, update vcap_get_rule() to always
> return an ERR_PTR() and update the error detection conditions to
> use IS_ERR(), which would be more cleaner.
>
> So se IS_ERR() to update the return value and fix the issue
> in lan966x_ptp_add_trap().
>
> Changes in v2:
> - Update vcap_get_rule() to always return an ERR_PTR().
> - Update the return value fix in lan966x_ptp_add_trap().
> - Update the return value check in sparx5_tc_free_rule_resources().
>
> Ruan Jinjie (3):
> net: microchip: vcap api: Always return ERR_PTR for vcap_get_rule()
> net: lan966x: Fix return value check for vcap_get_rule()
> net: microchip: sparx5: Update return value check for vcap_get_rule()
Thanks.
For the series,
Reviewed-by: Simon Horman <horms@...nel.org>
Powered by blists - more mailing lists