[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c20996aa-5c12-4af1-ae0d-838610cfee42@ideasonboard.com>
Date: Thu, 15 Dec 2022 18:56:24 +0530
From: Umang Jain <umang.jain@...asonboard.com>
To: Stefan Wahren <stefan.wahren@...e.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 Stefan,
On 12/15/22 5:00 PM, Stefan Wahren wrote:
> 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.
I agree with you on that front - I am still trying to understand the
bits of pieces of the vchiq driver as you can see it's not obvious to me.
I will try to address this is in v2 - after the series a bit more feedback.
>
> The rest of the series looks good to me.
Okay :-)
Thanks for prompt review.
>
> Best regards
>
Powered by blists - more mailing lists