From: simran singhal <singhalsimran0@gmail.com>
To: lars@metafoo.de
Cc: Michael.Hennerich@analog.com, jic23@kernel.org, knaack.h@gmx.de,
pmeerw@pmeerw.net, gregkh@linuxfoundation.org,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: [PATCH v3 0/2] Replace mlock with private lock and delete whitespaces
Date: Tue, 21 Mar 2017 23:33:54 +0530 [thread overview]
Message-ID: <1490119436-20042-1-git-send-email-singhalsimran0@gmail.com> (raw)
The patch series replaces mlock with a private lock for driver ad9834 and
Fix coding style issues related to white spaces.
v3:
-Using new private "lock" instead of using "buf_lock"
as it can cause deadlock.
-Sending it as a series of two patches.
v2:
-Using the existing buf_lock instead of lock.
simran singhal (2):
staging: iio: ade7753: Remove trailing whitespaces
staging: iio: ade7753: Replace mlock with driver private lock
drivers/staging/iio/meter/ade7753.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
--
2.7.4
next reply other threads:[~2017-03-21 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 18:03 simran singhal [this message]
2017-03-21 18:03 ` [PATCH v3 1/2] staging: iio: ade7753: Remove trailing whitespaces simran singhal
2017-03-22 20:25 ` Jonathan Cameron
2017-03-21 18:03 ` [PATCH v3 2/2] staging: iio: ade7753: Replace mlock with driver private lock simran singhal
[not found] ` <5d65a41d-5290-eb55-6452-7bb8bfbdd9f2@kernel.org>
2017-03-23 18:12 ` SIMRAN SINGHAL
2017-03-23 18:17 ` Jonathan Cameron
2017-03-21 18:50 ` [Outreachy kernel] [PATCH v3 0/2] Replace mlock with private lock and delete whitespaces 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=1490119436-20042-1-git-send-email-singhalsimran0@gmail.com \
--to=singhalsimran0@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=pmeerw@pmeerw.net \
/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).