From: Waiman Long <longman@redhat.com>
To: George Stark <gnstark@salutedevices.com>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>, Will Deacon <will@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: gregkh@linuxfoundation.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel@salutedevices.com" <kernel@salutedevices.com>
Subject: Re: [PATCH 1/2] locking/mutex: Clean up mutex.h
Date: Mon, 12 Feb 2024 22:28:37 -0500 [thread overview]
Message-ID: <a8313e5d-c4f2-4f4c-a05e-b87b2d694901@redhat.com> (raw)
In-Reply-To: <22c625f9-1750-4ade-b9c7-27b608c7f653@salutedevices.com>
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.
Cheers,
Longman
next prev parent reply other threads:[~2024-02-13 3:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 1:36 Waiman Long
2023-12-16 1:36 ` [PATCH 2/2] locking/rwsem: Make DEBUG_RWSEMS and PREEMPT_RT mutually exclusive Waiman Long
2023-12-16 11:47 ` [PATCH 1/2] locking/mutex: Clean up mutex.h George Stark
2023-12-16 12:07 ` Christophe JAILLET
2024-01-09 10:49 ` George Stark
2024-01-28 18:28 ` George Stark
2024-02-11 23:28 ` George Stark
2024-02-13 3:28 ` Waiman Long [this message]
2024-02-13 19:51 ` George Stark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8313e5d-c4f2-4f4c-a05e-b87b2d694901@redhat.com \
--to=longman@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--cc=gnstark@salutedevices.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@salutedevices.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®