From: Luis Chamberlain <mcgrof@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: david@redhat.com, patches@lists.linux.dev,
linux-modules@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, pmladek@suse.com,
petr.pavlu@suse.com, prarit@redhat.com,
torvalds@linux-foundation.org, gregkh@linuxfoundation.org,
rafael@kernel.org, christophe.leroy@csgroup.eu,
tglx@linutronix.de, peterz@infradead.org, song@kernel.org,
rppt@kernel.org, dave@stgolabs.net, vbabka@suse.cz,
mhocko@suse.com, dave.hansen@linux.intel.com,
colin.i.king@gmail.com, jim.cromie@gmail.com,
catalin.marinas@arm.com, jbaron@akamai.com,
rick.p.edgecombe@intel.com
Subject: Re: [PATCH v2 1/2] Change DEFINE_SEMAPHORE() to take a number argument
Date: Tue, 11 Apr 2023 21:05:12 -0700 [thread overview]
Message-ID: <ZDYt+PwRjr+BzeBz@bombadil.infradead.org> (raw)
In-Reply-To: <ZDB+zn3X4sac9DFU@casper.infradead.org>
On Fri, Apr 07, 2023 at 09:36:30PM +0100, Matthew Wilcox wrote:
> Or this:
>
> /*
> * Unlike mutexes, binary semaphores do not have an owner, so up() can
> * be called in a different thread from the one which called down().
> * It is also safe to call down_trylock() and up() from interrupt
> * context.
> */
I went with that. Thanks for helping me paint this shed!
Luis
next prev parent reply other threads:[~2023-04-12 4:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 20:35 [PATCH v2 0/2] kmod: simplify with a semaphore Luis Chamberlain
2023-04-05 20:35 ` [PATCH v2 1/2] Change DEFINE_SEMAPHORE() to take a number argument Luis Chamberlain
2023-04-07 16:38 ` Davidlohr Bueso
2023-04-07 20:36 ` Matthew Wilcox
2023-04-07 20:52 ` Linus Torvalds
2023-04-12 4:05 ` Luis Chamberlain [this message]
2023-04-08 8:22 ` Sergey Senozhatsky
2023-04-05 20:35 ` [PATCH v2 2/2] modules/kmod: replace implementation with a sempahore Luis Chamberlain
2023-04-07 17:19 ` Davidlohr Bueso
2023-04-11 8:42 ` David Hildenbrand
2023-04-13 9:44 ` Miroslav Benes
2023-04-13 16:38 ` Luis Chamberlain
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=ZDYt+PwRjr+BzeBz@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=colin.i.king@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-modules@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=patches@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=prarit@redhat.com \
--cc=rafael@kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rppt@kernel.org \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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