From: Mark Brown <broonie@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
Maciej Purski <m.purski@samsung.com>,
linux-omap@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Regulator regression in next-20180305
Date: Wed, 7 Mar 2018 14:45:05 +0000 [thread overview]
Message-ID: <20180307144505.GH7290@sirena.org.uk> (raw)
In-Reply-To: <CAOMZO5BPyY3WUYUhV76HGdb_NbCv9riFdtEFaku2k4dd9-A_FQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
On Tue, Mar 06, 2018 at 07:10:01PM -0300, Fabio Estevam wrote:
> Yesterday I spent a few hours trying to understand this locking issue,
> but didn't get any success on this task.
Right, so I'm thinking that if it's taking this much effort to think
about the problem we should just drop the patch set for now. I've moved
the code to a branch test/coupled in my git so it's not getting in
people's way in -next. Maciej, I suspect that you might be able to
reproduce this if you set supply names in the regulator definitons for
the PMICs on your boards. I think that's the difference here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-07 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 23:12 Tony Lindgren
2018-03-05 23:22 ` Fabio Estevam
2018-03-06 16:30 ` Mark Brown
2018-03-06 16:56 ` Fabio Estevam
2018-03-06 17:18 ` Tony Lindgren
2018-03-06 19:12 ` Mark Brown
2018-03-06 20:06 ` Fabio Estevam
2018-03-06 21:33 ` Mark Brown
2018-03-06 22:10 ` Fabio Estevam
2018-03-07 14:45 ` Mark Brown [this message]
2018-03-07 12:57 ` Maciej Purski
2018-03-07 14:10 ` Mark Brown
2018-03-07 14:37 ` Maciej Purski
2018-03-07 15:17 ` Tony Lindgren
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=20180307144505.GH7290@sirena.org.uk \
--to=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m.purski@samsung.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®