[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <129309f3-93d6-4926-8af1-b8d5ea995d48@stanley.mountain>
Date: Mon, 30 Sep 2024 14:08:26 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Przemek Kitszel <przemyslaw.kitszel@...el.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: linux-kernel@...r.kernel.org, Peter Zijlstra <peterz@...radead.org>,
amadeuszx.slawinski@...ux.intel.com,
Tony Nguyen <anthony.l.nguyen@...el.com>,
nex.sw.ncis.osdt.itp.upstreaming@...el.com, netdev@...r.kernel.org,
Andy Shevchenko <andriy.shevchenko@...el.com>
Subject: Re: [RFC PATCH] cleanup: make scoped_guard() to be return-friendly
On Mon, Sep 30, 2024 at 12:21:44PM +0200, Przemek Kitszel wrote:
>
> Most of the time it is just easier to bend your driver than change or
> extend the core of the kernel.
>
> There is actually scoped_cond_guard() which is a trylock variant.
>
> scoped_guard(mutex_try, &ts->mutex) you have found is semantically
> wrong and must be fixed.
What? I'm so puzzled by this conversation.
Anyway, I don't have a problem with your goal, but your macro is wrong and will
need to be re-written. You will need to update any drivers which use the
scoped_guard() for try locks. I don't care how you do that. Use
scoped_cond_guard() if you want or invent a new macro. But that work always
falls on the person changing the API. Plus, it's only the one tsc200x-core.c
driver so I don't understand why you're making a big deal about it.
regards,
dan carpenter
Powered by blists - more mailing lists