linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: Syed Nayyar Waris <syednwaris@gmail.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] counter: 104-quad-8: Add lock guards - generic interface
Date: Sun, 22 Mar 2020 17:58:31 +0000	[thread overview]
Message-ID: <20200322175831.74e10aa7@archlinux> (raw)
In-Reply-To: <20200318020506.GA45571@icarus>

On Tue, 17 Mar 2020 22:14:49 -0400
William Breathitt Gray <vilhelm.gray@gmail.com> wrote:

> On Mon, Mar 16, 2020 at 06:19:30PM +0530, Syed Nayyar Waris wrote:
> > Add lock protection from race conditions to 104-quad-8 counter driver
> > generic interface code changes. Mutex calls used for protection.
> > 
> > Fixes: f1d8a071d45b ("counter: 104-quad-8: Add Generic Counter interface
> > support")
> > 
> > Signed-off-by: Syed Nayyar Waris <syednwaris@gmail.com>
> > ---
> > Changes in v5:
> >  - Change spin lock calls to mutex lock calls
> >  - Modify the title description.  
> 
> Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>

Looks good.  I'm not sure right now which tree I'll take this through
(depends on whether it looks like we'll get an rc8 and hence I can sneak
it in for the coming merge window or not).

So poke me if I seem to have forgotten to apply this in a week or so.

Thanks,

Jonathan

  reply	other threads:[~2020-03-22 17:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 12:49 [PATCH v5 1/3] counter: 104-quad-8: Add lock guards - generic interface Syed Nayyar Waris
2020-03-18  2:14 ` William Breathitt Gray
2020-03-22 17:58   ` Jonathan Cameron [this message]
2020-03-30 18:24     ` Syed Nayyar Waris
2020-04-04 14:06       ` Jonathan Cameron
2020-06-07  3:58         ` Syed Nayyar Waris
2020-06-07  4:09           ` William Breathitt Gray
2020-06-07  5:30             ` Syed Nayyar Waris
2020-06-08 11:08               ` Jonathan Cameron

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=20200322175831.74e10aa7@archlinux \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syednwaris@gmail.com \
    --cc=vilhelm.gray@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;
as well as URLs for NNTP newsgroup(s).