From: Alison Schofield <amsfield22@gmail.com>
To: outreachy-kernel@googlegroups.com
Subject: [PATCH v3 0/4] staging: wilc1000: use completions in host_interface
Date: Mon, 14 Mar 2016 10:33:40 -0700 [thread overview]
Message-ID: <cover.1457974909.git.amsfield22@gmail.com> (raw)
This patchset replaces the semaphores in struct host_if_drv with the
more preferred locking mechanisms completions.
Each semaphore was used in the send/receive of HOST_IF_MSG_* messages.
Each builds and queues a message (LOCK!) and then a corresponding
"Handler" function is called from the hostIFthread() when the message
is returned (UNLOCK).
Note that in Patch 4 you will not see a 1:1 correspondence between
wait_for_completion and complete. Whereas 6 different functions build
the KEY messages, only 5 handlers are used.
Changes in v2
- spun off patch 5 as a separate patch so that this set only includes
semaphores->completions
- rebase/rebuild
Changes in v3
- rebase/rebuild
Alison Schofield (4):
staging: wilc1000: replace semaphore sem_inactive_time with a
completion
staging: wilc1000: replace semaphore sem_get_rssi with a completion
staging: wilc1000: replace sem_test_disconn_block with a completion
staging: wilc1000: replace sem_test_key_block with a completion
drivers/staging/wilc1000/host_interface.c | 43 ++++++++++++++++---------------
drivers/staging/wilc1000/host_interface.h | 8 +++---
2 files changed, 26 insertions(+), 25 deletions(-)
--
2.1.4
next reply other threads:[~2016-03-14 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 17:33 Alison Schofield [this message]
2016-03-14 17:34 ` [PATCH v3 1/4] staging: wilc1000: replace semaphore sem_inactive_time with a completion Alison Schofield
2016-03-14 17:34 ` [PATCH v3 2/4] staging: wilc1000: replace semaphore sem_get_rssi " Alison Schofield
2016-03-14 17:35 ` [PATCH v3 3/4] staging: wilc1000: replace sem_test_disconn_block " Alison Schofield
2016-03-14 17:35 ` [PATCH v3 4/4] staging: wilc1000: replace sem_test_key_block " Alison Schofield
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=cover.1457974909.git.amsfield22@gmail.com \
--to=amsfield22@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.