From: Daniel Wagner <wagi@monom.org>
To: linux-kernel@vger.kernel.org
Cc: Alex Dubov <oakad@yahoo.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sudeep Dutt <sudeep.dutt@intel.com>,
Wolfram Sang <wsa@the-dreams.de>,
Daniel Wagner <daniel.wagner@bmw-carit.de>
Subject: [PATCH 0/4] Use complete() instead of complete_all()
Date: Fri, 5 Aug 2016 11:25:59 +0200 [thread overview]
Message-ID: <1470389163-4594-1-git-send-email-wagi@monom.org> (raw)
From: Daniel Wagner <daniel.wagner@bmw-carit.de>
Hi,
Using complete_all() is not wrong per se but it suggest that there
might be more than one reader. For -rt I am reviewing all
complete_all() users and would like to leave only the real ones in the
tree. The main problem for -rt about complete_all() is that it can be
uses inside IRQ context and that can lead to unbounded amount work
inside the interrupt handler. That is a no no for -rt.
The patches grouped per subsystem and in small batches to allow
reviewing. Unfortanatly I am not so good in coming up with unique
commit message, so please bear with me in that regard. I could also
squash them together, although each patch containts a very short
reasoning why there is only one waiter. Let me know what you rather
prefer. One patch which updates all complete_all() users or those 4
patches with some reasoning.
It is only test compiled because I don't have the all the hardware.
cheers,
daniel
Daniel Wagner (4):
misc: mic: scif: use complete() instead of complete_all()
misc: mic: vop: use complete() instead of complete_all()
misc: ti-st: use complete() instead of complete_all()
misc: tifm: use complete() instead of complete_all()
drivers/misc/mic/scif/scif_nodeqp.c | 2 +-
drivers/misc/mic/vop/vop_main.c | 2 +-
drivers/misc/ti-st/st_kim.c | 2 +-
drivers/misc/tifm_7xx1.c | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
--
2.7.4
next reply other threads:[~2016-08-05 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 9:25 Daniel Wagner [this message]
2016-08-05 9:26 ` [PATCH 1/4] misc: mic: scif: use " Daniel Wagner
2016-08-05 9:26 ` [PATCH 2/4] misc: mic: vop: " Daniel Wagner
2016-08-05 9:26 ` [PATCH 3/4] misc: ti-st: " Daniel Wagner
2016-08-05 9:26 ` [PATCH 4/4] misc: tifm: " Daniel Wagner
2016-08-14 22:51 ` [PATCH 0/4] Use " Wolfram Sang
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=1470389163-4594-1-git-send-email-wagi@monom.org \
--to=wagi@monom.org \
--cc=ashutosh.dixit@intel.com \
--cc=daniel.wagner@bmw-carit.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.com \
--cc=sudeep.dutt@intel.com \
--cc=wsa@the-dreams.de \
/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®