[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c963fd9-97c9-d513-a8ae-5d3f22ef57cc@i2se.com>
Date: Thu, 15 Dec 2022 12:30:29 +0100
From: Stefan Wahren <stefan.wahren@...e.com>
To: Umang Jain <umang.jain@...asonboard.com>,
linux-staging@...ts.linux.dev,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Kees Cook <keescook@...omium.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Florian Fainelli <f.fainelli@...il.com>,
Adrien Thierry <athierry@...hat.com>,
Dan Carpenter <error27@...il.com>,
Dave Stevenson <dave.stevenson@...pberrypi.com>,
Kieran Bingham <kieran.bingham@...asonboard.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: Re: [PATCH 3/7] staging: vc04_services: Drop VCHIQ_ERROR usage
Hi Umang,
thanks for taking care of this.
Am 15.12.22 um 07:58 schrieb Umang Jain:
> Drop the usage of VCHIQ_ERROR vchiq_status enum type. Replace it with
> -EINVAL to report the error.
I would prefer to use adequate error codes like ENOMEM and so on. I
agree simply replacing all VCHIQ_ERROR with -EINVAL is easier, but
wasn't the real intention of the TODO item.
The rest of the series looks good to me.
Best regards
Powered by blists - more mailing lists