[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <63e0d41a-92b6-4596-ae54-d6bc2624e63d@salutedevices.com>
Date: Tue, 13 Feb 2024 22:51:53 +0300
From: George Stark <gnstark@...utedevices.com>
To: Waiman Long <longman@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
Boqun Feng <boqun.feng@...il.com>, Will Deacon <will@...nel.org>, Ingo Molnar
<mingo@...hat.com>, Andrew Morton <akpm@...ux-foundation.org>
CC: <gregkh@...uxfoundation.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "kernel@...utedevices.com"
<kernel@...utedevices.com>
Subject: Re: [PATCH 1/2] locking/mutex: Clean up mutex.h
On 2/13/24 06:28, Waiman Long wrote:
>
> On 2/11/24 18:28, George Stark wrote:
>> Hello
>>
>> Excuse me, this is my 4th letter here since December 2023 and there's
>> no response unfortunately.
>>
>>
>> Just to recall that we had the discussion in December 2023 about
>> implementing devm_mutex_init. We came to conclusion that the only
>> effective way to do it in include/linux/mutex.h but mutex.h requires
>> some cleanups to simplify the devm_mutex_init patch.
>> mutex.h owners proposed such a cleanup patch themselves and there's no
>> progress since that. How can we move forward on those patches?
>>
>> Cleanup patch:
>> https://lore.kernel.org/lkml/20231216013656.1382213-1-longman@redhat.com/
>>
>> Original problem that requires devm_mutex_init and discussion:
>> https://lore.kernel.org/lkml/ZcZeRmVjEPhVPW9-@smile.fi.intel.com/T/#m0f514f8f96e18db9568f84b2df37aaf648874a4a
>
> Sorry for my late reply. My cleanup patch was sent at the later half of
> Dec 2023. It is probably not a good time as maintainers are either busy
> or taking time off. I have resent the patch again with other cleanup
> patches. Hopefully those patches can be merged soon.
Hello Waiman.
Good to see you again. I'm sorry if I was too impatient. Thanks for
updating your patch series.
>
> Cheers,
> Longman
>
--
Best regards
George
Powered by blists - more mailing lists