From: Zack Rusin <zackr@vmware.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] locking/rwsem: Add down_write_interruptible
Date: Tue, 9 Mar 2021 10:37:49 -0500 [thread overview]
Message-ID: <cbaaf6b6-9981-997a-02ed-4d6055fd9833@vmware.com> (raw)
In-Reply-To: <YEc2ry1h1qC3N2m9@hirez.programming.kicks-ass.net>
On 3/9/21 3:49 AM, Peter Zijlstra wrote:
> On Mon, Mar 08, 2021 at 03:54:55PM -0500, Zack Rusin wrote:
>> Add an interruptible version of down_write. It's the other
>> side of the already implemented down_read_interruptible.
>> It allows drivers which used custom locking code to
>> support interruptible rw semaphores to switch over
>> to rwsem.
>>
>> Cc: Peter Zijlstra <peterz@infradead.org>
>> Cc: Ingo Molnar <mingo@redhat.com>
>> Cc: Will Deacon <will@kernel.org>
>> Cc: linux-kernel@vger.kernel.org
>> Cc: dri-devel@lists.freedesktop.org
>
> No SoB!
Ah, sorry, fixed that locally.
> Assuning you actually wrote and and simply forgot to add it, the patch
> does look ok, so:
>
> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Thank you. I didn't want to bother you with the code in vmwgfx, so I
only sent it to the lists (it was missing SoB as well):
https://lore.kernel.org/patchwork/patch/1391810/
z
next prev parent reply other threads:[~2021-03-09 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 20:54 [PATCH 0/2] locking/rwsem: Add down_write_interruptible and use it Zack Rusin
2021-03-08 20:54 ` [PATCH 1/2] locking/rwsem: Add down_write_interruptible Zack Rusin
2021-03-09 8:49 ` Peter Zijlstra
2021-03-09 15:37 ` Zack Rusin [this message]
2021-03-08 20:54 ` [PATCH 2/2] drm/vmwgfx: Remove custom locking code Zack Rusin
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=cbaaf6b6-9981-997a-02ed-4d6055fd9833@vmware.com \
--to=zackr@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).