[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f382ce84-8a47-6315-9bdb-9d9957f1800b@lechnology.com>
Date: Sat, 20 Feb 2021 10:48:45 -0600
From: David Lechner <david@...hnology.com>
To: William Breathitt Gray <vilhelm.gray@...il.com>, jic23@...nel.org
Cc: kernel@...gutronix.de, linux-stm32@...md-mailman.stormreply.com,
a.fatoum@...gutronix.de, kamel.bouhara@...tlin.com,
gwendal@...omium.org, alexandre.belloni@...tlin.com,
linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, syednwaris@...il.com,
patrick.havelange@...ensium.com, fabrice.gasnier@...com,
mcoquelin.stm32@...il.com, alexandre.torgue@...com,
o.rempel@...gutronix.de
Subject: Re: [PATCH v8 10/22] counter: Standardize to ERANGE for limit
exceeded errors
On 2/12/21 6:13 AM, William Breathitt Gray wrote:
> ERANGE is a semantically better error code to return when an argument
> value falls outside the supported limit range of a device.
>
> Cc: Syed Nayyar Waris <syednwaris@...il.com>
> Cc: Fabrice Gasnier <fabrice.gasnier@...com>
> Cc: Maxime Coquelin <mcoquelin.stm32@...il.com>
> Cc: Alexandre Torgue <alexandre.torgue@...com>
> Signed-off-by: William Breathitt Gray <vilhelm.gray@...il.com>
> ---
Reviewed-by: David Lechner <david@...hnology.com>
(I agree with William's assessment that this use of ERANGE
is consistent with other uses in the kernel.)
Powered by blists - more mailing lists