All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shreeya Patel <shreeya.patel23498@gmail.com>
To: lars@metafoo.de, 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
Cc: Shreeya Patel <shreeya.patel23498@gmail.com>
Subject: [PATCH 0/2] Remove usage of mlocks from ade7758 file
Date: Tue,  6 Feb 2018 01:05:50 +0530	[thread overview]
Message-ID: <cover.1517845616.git.shreeya.patel23498@gmail.com> (raw)

This patchset has been introduced for the removal of mlocks
from the ade7758 file and replace it with the already established
buf_lock.
Patch *[1/2] removes the unnecessary mlocks i.e. which are
taken around the read cases.
Patch *[2/2] replaces other mlocks with buf_locks and introduces
unlocked forms of read and write registers so as to avoid nested 
locks. Also some additional cleanups like moving the locks to where
they are required to protect, are made to improve the code clarity.

This patchset has been introduced after the revisions done on the
patch *[2/2] and also there was the need of patch *[1/2].


Shreeya Patel (2):
  Staging: iio: ade7758: Remove iio_dev mlock
  Staging: iio: ade7758: Expand buf_lock to cover both buffer and state
    protection

 drivers/staging/iio/meter/ade7758.h      |  2 +-
 drivers/staging/iio/meter/ade7758_core.c | 54 ++++++++++++++++++++++----------
 2 files changed, 39 insertions(+), 17 deletions(-)

-- 
2.7.4

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

WARNING: multiple messages have this Message-ID (diff)
From: Shreeya Patel <shreeya.patel23498@gmail.com>
To: lars@metafoo.de, 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
Cc: Shreeya Patel <shreeya.patel23498@gmail.com>
Subject: [PATCH 0/2] Remove usage of mlocks from ade7758 file
Date: Tue,  6 Feb 2018 01:05:50 +0530	[thread overview]
Message-ID: <cover.1517845616.git.shreeya.patel23498@gmail.com> (raw)

This patchset has been introduced for the removal of mlocks
from the ade7758 file and replace it with the already established
buf_lock.
Patch *[1/2] removes the unnecessary mlocks i.e. which are
taken around the read cases.
Patch *[2/2] replaces other mlocks with buf_locks and introduces
unlocked forms of read and write registers so as to avoid nested 
locks. Also some additional cleanups like moving the locks to where
they are required to protect, are made to improve the code clarity.

This patchset has been introduced after the revisions done on the
patch *[2/2] and also there was the need of patch *[1/2].


Shreeya Patel (2):
  Staging: iio: ade7758: Remove iio_dev mlock
  Staging: iio: ade7758: Expand buf_lock to cover both buffer and state
    protection

 drivers/staging/iio/meter/ade7758.h      |  2 +-
 drivers/staging/iio/meter/ade7758_core.c | 54 ++++++++++++++++++++++----------
 2 files changed, 39 insertions(+), 17 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-02-05 19:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 19:35 Shreeya Patel [this message]
2018-02-05 19:35 ` [PATCH 0/2] Remove usage of mlocks from ade7758 file Shreeya Patel
2018-02-05 19:38 ` [PATCH 1/2] Staging: iio: ade7758: Remove iio_dev mlock Shreeya Patel
2018-02-05 19:38   ` Shreeya Patel
2018-02-06  7:23   ` Ardelean, Alexandru
2018-02-05 19:40 ` [PATCH v5 2/2] Staging: iio: ade7758: Expand buf_lock to cover both buffer and state protection Shreeya Patel
2018-02-05 19:40   ` Shreeya Patel
2018-02-06  7:32   ` Ardelean, Alexandru

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.1517845616.git.shreeya.patel23498@gmail.com \
    --to=shreeya.patel23498@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=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 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.