From: Rohit Sarkar <rohitsarkar5398@gmail.com>
To: linux-iio@vger.kernel.org
Cc: rohitsarkar5398@gmail.com
Subject: query about locking in IIO
Date: Tue, 25 Feb 2020 22:41:50 +0530 [thread overview]
Message-ID: <20200225171150.GD24663@SARKAR> (raw)
Hi,
Could someone explain why using indio_dev->mlock directly is a bad idea?
Further examples of cases where it cannot be replaced will be helpful
Thanks,
Rohit
next reply other threads:[~2020-02-25 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 17:11 Rohit Sarkar [this message]
2020-02-26 6:54 ` query about locking in IIO Ardelean, Alexandru
2020-02-26 17:25 ` Rohit Sarkar
2020-02-27 6:58 ` Ardelean, Alexandru
2020-02-28 13:24 ` Jonathan Cameron
2020-02-28 19:22 ` Rohit Sarkar
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=20200225171150.GD24663@SARKAR \
--to=rohitsarkar5398@gmail.com \
--cc=linux-iio@vger.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 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.