[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191102103515.GA135926@kroah.com>
Date: Sat, 2 Nov 2019 11:35:15 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Davidlohr Bueso <dave@...olabs.net>
Cc: eric@...olt.net, wahrenst@....net, devel@...verdev.osuosl.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH resend] staging: vc04_services: replace
g_free_fragments_mutex with spinlock
On Fri, Nov 01, 2019 at 11:29:49AM -0700, Davidlohr Bueso wrote:
> There is no need to be using a semaphore, or a sleeping lock
> in the first place: critical region is extremely short, does not
> call into any blocking calls and furthermore lock and unlocking
> operations occur in the same context.
>
> Get rid of another semaphore user by replacing it with a spinlock.
>
> Signed-off-by: Davidlohr Bueso <dave@...olabs.net>
> ---
> This is in an effort to further reduce semaphore users in the kernel.
>
> This is a resend, which just seems simpler given the confusions.
>
> .../staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
This patch does not apply to my tree at all, what did you make it
against?
Please fix up and resend.
thanks,
greg k-h
Powered by blists - more mailing lists