From: Alison Schofield <amsfield22@gmail.com>
To: SIMRAN SINGHAL <singhalsimran0@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Pete Meerwald-Stadler <pmeerw@pmeerw.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH] staging: iio: ade7753: replace mlock with driver private lock
Date: Sun, 12 Mar 2017 22:29:58 -0700 [thread overview]
Message-ID: <20170313052956.GA18681@d830.WORKGROUP> (raw)
In-Reply-To: <CALrZqyOkKMb1bM0V=L7G7v+64N4FHuYUSoW1+8rvcZQU-816sg@mail.gmail.com>
On Mon, Mar 13, 2017 at 09:28:34AM +0530, SIMRAN SINGHAL wrote:
> On Mon, Mar 13, 2017 at 12:03 AM, Alison Schofield <amsfield22@gmail.com> wrote:
> > On Sun, Mar 12, 2017 at 07:02:50PM +0530, simran singhal wrote:
> >> The IIO subsystem is redefining iio_dev->mlock to be used by
> >> the IIO core only for protecting device operating mode changes.
> >> ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes.
> >>
> >> In this driver, mlock was being used to protect hardware state
> >> changes. Replace it with a lock in the devices global data.
> >>
> >> Fix some coding style issues related to white space also.
> >>
> >> Signed-off-by: simran singhal <singhalsimran0@gmail.com>
> >
> > Hi Simran, This looks good to me. Let's see what the
> > reviewers say. I think the white space stuff is ok,
> > since it was right where you were editing.
> > alisons
> >
> Alison, so sending this patch here on outreachy mailing list is fine.
> Still confuse :P
You are OK. You sent it to everyone suggested in the Task Description.
This patch was sent before I posted the Task Description. I'm assuming
that since then you've found the posted Task:
https://kernelnewbies.org/IIO_tasks
Find Coding Task 2 --> "PATCHES need to be sent to all of:"
>
> >> ---
> >> drivers/staging/iio/meter/ade7753.c | 14 ++++++++------
> >> 1 file changed, 8 insertions(+), 6 deletions(-)
> >>
> >> diff --git a/drivers/staging/iio/meter/ade7753.c b/drivers/staging/iio/meter/ade7753.c
> >> index dfd8b71..ca99d82 100644
> >> --- a/drivers/staging/iio/meter/ade7753.c
> >> +++ b/drivers/staging/iio/meter/ade7753.c
> >> @@ -81,12 +81,14 @@
> >> * @tx: transmit buffer
> >> * @rx: receive buffer
> >> * @buf_lock: mutex to protect tx and rx
> >> + * @lock: protect sensor state
> >> **/
> >> struct ade7753_state {
> >> - struct spi_device *us;
> >> - struct mutex buf_lock;
> >> - u8 tx[ADE7753_MAX_TX] ____cacheline_aligned;
> >> - u8 rx[ADE7753_MAX_RX];
> >> + struct spi_device *us;
> >> + struct mutex buf_lock;
> >> + struct mutex lock; /* protect sensor state */
> >> + u8 tx[ADE7753_MAX_TX] ____cacheline_aligned;
> >> + u8 rx[ADE7753_MAX_RX];
> >> };
> >>
> >> static int ade7753_spi_write_reg_8(struct device *dev,
> >> @@ -484,7 +486,7 @@ static ssize_t ade7753_write_frequency(struct device *dev,
> >> if (!val)
> >> return -EINVAL;
> >>
> >> - mutex_lock(&indio_dev->mlock);
> >> + mutex_lock(&st->lock);
> >>
> >> t = 27900 / val;
> >> if (t > 0)
> >> @@ -505,7 +507,7 @@ static ssize_t ade7753_write_frequency(struct device *dev,
> >> ret = ade7753_spi_write_reg_16(dev, ADE7753_MODE, reg);
> >>
> >> out:
> >> - mutex_unlock(&indio_dev->mlock);
> >> + mutex_unlock(&st->lock);
> >>
> >> return ret ? ret : len;
> >> }
> >> --
> >> 2.7.4
> >>
> >> --
> >> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> >> To post to this group, send email to outreachy-kernel@googlegroups.com.
> >> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20170312133250.GA7772%40singhal-Inspiron-5558.
> >> For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2017-03-13 5:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 13:32 simran singhal
2017-03-12 18:33 ` [Outreachy kernel] " Alison Schofield
2017-03-13 3:58 ` SIMRAN SINGHAL
2017-03-13 5:29 ` Alison Schofield [this message]
2017-03-13 12:00 ` Lars-Peter Clausen
2017-03-13 12:33 ` SIMRAN SINGHAL
2017-03-13 13:34 ` Lars-Peter Clausen
2017-03-17 9:32 ` [Outreachy kernel] " Gargi Sharma
2017-03-19 10:31 ` Jonathan Cameron
2017-03-19 13:16 ` Gargi Sharma
2017-03-19 17:08 ` Jonathan Cameron
2017-03-19 18:02 ` Gargi Sharma
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=20170313052956.GA18681@d830.WORKGROUP \
--to=amsfield22@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 \
--cc=singhalsimran0@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome