[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37779db2-114c-4df6-97fd-2444bdad5529@gmx.net>
Date: Fri, 14 Jun 2024 13:00:38 +0200
From: Stefan Wahren <wahrenst@....net>
To: Kieran Bingham <kieran.bingham@...asonboard.com>,
Umang Jain <umang.jain@...asonboard.com>,
Florian Fainelli <florian.fainelli@...adcom.com>,
linux-rpi-kernel@...ts.infradead.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Broadcom internal kernel review list
<bcm-kernel-feedback-list@...adcom.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Dave Stevenson <dave.stevenson@...pberrypi.org>, detule
<ogjoneski@...il.com>, Dan Carpenter <dan.carpenter@...aro.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
"open list:STAGING SUBSYSTEM" <linux-staging@...ts.linux.dev>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [v2 PATCH] staging: vc04_services: vchiq_arm: Fix initialisation
check
Hi Kieran,
Am 14.06.24 um 12:43 schrieb Kieran Bingham:
> The vchiq_state used to be obtained through an accessor
> which would validate that the VCHIQ had been initialised
> correctly with the remote.
>
> In commit 42a2f6664e18 ("staging: vc04_services: Move global g_state to
> vchiq_state") the global state was moved to the vchiq_mgnt structures
> stored as a vchiq instance specific context. This conversion removed the
> helpers and instead replaced users of this helper with the assumption
> that the state is always available and the remote connected.
>
> Fix this broken assumption by re-introducing the logic that was lost
> during the conversion.
>
> Fixes: 42a2f6664e18 ("staging: vc04_services: Move global g_state to vchiq_state")
> Signed-off-by: Kieran Bingham <kieran.bingham@...asonboard.com>
> ---
> v2:
> - No change, just resend
what happen to my comments for the first version?
Powered by blists - more mailing lists