[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZBMJc9abj/DP4RiN@nanopsycho>
Date: Thu, 16 Mar 2023 13:20:03 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Vadim Fedorenko <vadfed@...a.com>
Cc: Jakub Kicinski <kuba@...nel.org>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>,
Jonathan Lemon <jonathan.lemon@...il.com>,
Paolo Abeni <pabeni@...hat.com>,
Vadim Fedorenko <vadim.fedorenko@...ux.dev>, poros@...hat.com,
mschmidt@...hat.com, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
Milena Olech <milena.olech@...el.com>,
Michal Michalik <michal.michalik@...el.com>
Subject: Re: [PATCH RFC v6 2/6] dpll: Add DPLL framework base functions
Sun, Mar 12, 2023 at 03:28:03AM CET, vadfed@...a.com wrote:
[...]
>+/**
>+ * dpll_pin_unregister - deregister dpll pin from dpll device
>+ * @dpll: registered dpll pointer
>+ * @pin: pointer to a pin
>+ *
>+ * Note: It does not free the memory
>+ */
>+int dpll_pin_unregister(struct dpll_device *dpll, struct dpll_pin *pin)
Make this return void. Function does not report anything useful,
non-0 is only in case of WARN_ON. Nobody is going to check that ever
anyway.
>+{
>+ if (WARN_ON(xa_empty(&dpll->pin_refs)))
>+ return -ENOENT;
>+
>+ mutex_lock(&dpll_device_xa_lock);
>+ mutex_lock(&dpll_pin_xa_lock);
>+ __dpll_pin_unregister(dpll, pin);
>+ mutex_unlock(&dpll_pin_xa_lock);
>+ mutex_unlock(&dpll_device_xa_lock);
>+
>+ return 0;
>+}
>+EXPORT_SYMBOL_GPL(dpll_pin_unregister);
[...]
Powered by blists - more mailing lists