From: Mark Brown <broonie@kernel.org>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: linux-kernel@vger.kernel.org, kbuild-all@01.org
Subject: Re: drivers/spi/spi.c:1160:3-9: preceding lock on line 1153
Date: Tue, 9 Aug 2016 17:31:31 +0100 [thread overview]
Message-ID: <20160809163131.GC9347@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.10.1608091818440.2911@hadrien>
[-- Attachment #1: Type: text/plain, Size: 2705 bytes --]
On Tue, Aug 09, 2016 at 06:19:13PM +0200, Julia Lawall wrote:
> Looks worth checking.
I don't really have any idea what this is trying to tell me, sorry.
>
> julia
>
> ---------- Forwarded message ----------
> Date: Wed, 10 Aug 2016 00:17:07 +0800
> From: kbuild test robot <fengguang.wu@intel.com>
> To: kbuild@01.org
> Cc: Julia Lawall <julia.lawall@lip6.fr>
> Subject: drivers/spi/spi.c:1160:3-9: preceding lock on line 1153
>
> CC: kbuild-all@01.org
> CC: linux-kernel@vger.kernel.org
> TO: Mark Brown <broonie@kernel.org>
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 81abf2525827b29839a78fd55ab0699f033c41a5
> commit: ef4d96ec4ad947360f48677b6007a4c77953b090 spi: Split bus and I/O locking
> date: 2 weeks ago
> :::::: branch date: 18 hours ago
> :::::: commit date: 2 weeks ago
>
> >> drivers/spi/spi.c:1160:3-9: preceding lock on line 1153
>
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git remote update linus
> git checkout ef4d96ec4ad947360f48677b6007a4c77953b090
> vim +1160 drivers/spi/spi.c
>
> ffbbdd213 Linus Walleij 2012-02-22 1147 if (master->busy)
> ffbbdd213 Linus Walleij 2012-02-22 1148 was_busy = true;
> ffbbdd213 Linus Walleij 2012-02-22 1149 else
> ffbbdd213 Linus Walleij 2012-02-22 1150 master->busy = true;
> ffbbdd213 Linus Walleij 2012-02-22 1151 spin_unlock_irqrestore(&master->queue_lock, flags);
> ffbbdd213 Linus Walleij 2012-02-22 1152
> ef4d96ec4 Mark Brown 2016-07-21 @1153 mutex_lock(&master->io_mutex);
> ef4d96ec4 Mark Brown 2016-07-21 1154
> 49834de23 Mark Brown 2013-07-28 1155 if (!was_busy && master->auto_runtime_pm) {
> 49834de23 Mark Brown 2013-07-28 1156 ret = pm_runtime_get_sync(master->dev.parent);
> 49834de23 Mark Brown 2013-07-28 1157 if (ret < 0) {
> 49834de23 Mark Brown 2013-07-28 1158 dev_err(&master->dev, "Failed to power device: %d\n",
> 49834de23 Mark Brown 2013-07-28 1159 ret);
> 49834de23 Mark Brown 2013-07-28 @1160 return;
> 49834de23 Mark Brown 2013-07-28 1161 }
> 49834de23 Mark Brown 2013-07-28 1162 }
> 49834de23 Mark Brown 2013-07-28 1163
>
> :::::: The code at line 1160 was first introduced by commit
> :::::: 49834de234f3cf592c3d242c889ca603db8e7050 spi: Provide core support for runtime PM during transfers
>
> :::::: TO: Mark Brown <broonie@linaro.org>
> :::::: CC: Mark Brown <broonie@linaro.org>
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-08-09 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 16:19 drivers/spi/spi.c:1160:3-9: preceding lock on line 1153 Julia Lawall
2016-08-09 16:31 ` Mark Brown [this message]
2016-08-09 16:35 ` Julia Lawall
2016-08-09 16:43 ` Mark Brown
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=20160809163131.GC9347@sirena.org.uk \
--to=broonie@kernel.org \
--cc=julia.lawall@lip6.fr \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
/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