[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YyHrT6q9fockgPjl@kroah.com>
Date: Wed, 14 Sep 2022 16:55:11 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Manjunatha Venkatesh <manjunatha.venkatesh@....com>
Cc: linux-kernel@...r.kernel.org, will@...nel.org, axboe@...nel.dk,
robh+dt@...nel.org, mb@...htnvm.io, ckeepax@...nsource.cirrus.com,
arnd@...db.d, mst@...hat.com, javier@...igon.com,
mikelley@...rosoft.com, jasowang@...hat.com,
sunilmut@...rosoft.com, bjorn.andersson@...aro.org,
krzysztof.kozlowski+dt@...aro.org, devicetree@...r.kernel.org,
ashish.deshpande@....com, rvmanjumce@...il.com
Subject: Re: [PATCH v5 2/2] misc: nxp-sr1xx: UWB driver support for sr1xx
series chip
On Wed, Sep 14, 2022 at 07:59:44PM +0530, Manjunatha Venkatesh wrote:
> +/**
> + * sr1xx_dev_transceive
> + * @op_mode indicates write/read operation
> + *
> + * Write and Read logic implemented under same api with
> + * mutex lock protection so write and read synchronized
> + *
> + * During Uwb ranging sequence(read) need to block write sequence
> + * in order to avoid some race condition scenarios.
> + *
> + * Returns : Number of bytes write/read if read is success else (-1)
I'm sure I mentioned this before, but NEVER use magic "-1" as an error
value. Use the real in-kernel -ERROR numbers for error codes please.
This needs to be fixed in many places in this code.
thanks,
greg k-h
Powered by blists - more mailing lists