From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: rtc-linux@googlegroups.com,
Oleksij Rempel <fixed-term.Oleksij.Rempel@de.bosch.com>
Subject: [rtc-linux] Re: [PATCH] rtc: rv8803: convert spin_lock to mutex_lock
Date: Sat, 20 Feb 2016 15:13:39 +0100 [thread overview]
Message-ID: <20160220141339.GG2222@piout.net> (raw)
In-Reply-To: <1454589920-32738-1-git-send-email-dirk.behme@de.bosch.com>
Hi,
On 04/02/2016 at 13:45:20 +0100, Dirk Behme wrote :
> From: Oleksij Rempel <fixed-term.Oleksij.Rempel@de.bosch.com>
>
> Fix a scheduling while atomic issue caused by rv8803_set_time()
> holding a spinlock during the call to i2c_smbus_read_byte_data().
>
> Signed-off-by: Oleksij Rempel <fixed-term.Oleksij.Rempel@de.bosch.com>
> ---
> drivers/rtc/rtc-rv8803.c | 40 +++++++++++++++++++---------------------
> 1 file changed, 19 insertions(+), 21 deletions(-)
>
This didn't apply cleanly but I fixed it up.
Applied, thanks.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2016-02-20 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 12:45 [PATCH] rtc: rv8803: convert spin_lock to mutex_lock Dirk Behme
2016-02-17 16:55 ` dirk.behme
2016-02-20 14:13 ` Alexandre Belloni [this message]
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=20160220141339.GG2222@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=dirk.behme@de.bosch.com \
--cc=fixed-term.Oleksij.Rempel@de.bosch.com \
--cc=rtc-linux@googlegroups.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