From: Mark Brown <broonie@kernel.org>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: nikita.yoush@cogentembedded.com, cphealy@gmail.com,
huangtao@rock-chips.com, xxx@rock-chips.com,
jay.xu@rock-chips.com, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: fix up the regmap lock error
Date: Thu, 22 Sep 2016 11:23:09 +0100 [thread overview]
Message-ID: <20160922102309.GI7994@sirena.org.uk> (raw)
In-Reply-To: <1474539465-12487-1-git-send-email-zhangqing@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 791 bytes --]
On Thu, Sep 22, 2016 at 06:17:45PM +0800, Elaine Zhang wrote:
> Regmap lock is taken in regmap_update_bits_base() and then
> regcache_drop_region() tries to take it again.
> which added in commit 815806e39bf6
> ("regmap: drop cache if the bus transfer error")
Someone already sent a change for this.
> Backtrace:
> [<8068ab7c>] (__schedule) from [<8068b1c4>] (schedule+0xb8/0xd0)
> [<8068b10c>] (schedule) from [<8068b61c>] (schedule_preempt_disabled+0x20/0x2c)
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative then it's
usually better to pull out the relevant sections.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-09-22 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 10:17 [PATCH] regmap: fix up the regmap lock error Elaine Zhang
2016-09-22 10:23 ` Mark Brown [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=20160922102309.GI7994@sirena.org.uk \
--to=broonie@kernel.org \
--cc=cphealy@gmail.com \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nikita.yoush@cogentembedded.com \
--cc=xxx@rock-chips.com \
--cc=zhangqing@rock-chips.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