From: Mark Brown <broonie@kernel.org>
To: Torsten Duwe <duwe@lst.de>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] regulator: Defer init completion for a while after late_initcall
Date: Sun, 1 Dec 2019 23:49:11 +0000 [thread overview]
Message-ID: <20191201234911.GC1998@sirena.org.uk> (raw)
In-Reply-To: <20191130152700.GA14121@lst.de>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
On Sat, Nov 30, 2019 at 04:27:00PM +0100, Torsten Duwe wrote:
> Well, actually the 4 lines above give a good hint :) of_get_regulator()
> will look for "dvdd25-supply-supply". I'm fairly relieved that even you
> didn't spot this right away. The fix just went to dri-devel, you're Cc'ed.
> Unfortunately the documentation for this is buried in the git commit log.
Glad you got to the bottom of this! Like I said in reply to your
fix (which I saw first) this is covered in the DT binding
documentation for the regultaor API.
> For the record: I'm still convinced that the original change can uncover
> bugs unexpectedly, and is not suited for -stable.
Yeah, it's definitely at the upper limit of what I consider safe
for stable but it seems to fit the risk profile of what stable
wants to include these days and there was demand for it from
people working on DT based laptops and desktops.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-12-01 23:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 12:42 [PATCH] regulator: Defer init completion for a while after late_initcall Mark Brown
2019-09-04 17:53 ` Applied "regulator: Defer init completion for a while after late_initcall" to the regulator tree Mark Brown
2019-11-16 12:52 ` [PATCH] regulator: Defer init completion for a while after late_initcall Torsten Duwe
2019-11-18 12:46 ` Mark Brown
2019-11-18 16:41 ` Torsten Duwe
2019-11-18 16:56 ` Mark Brown
2019-11-18 19:40 ` Torsten Duwe
2019-11-18 20:29 ` Mark Brown
2019-11-30 15:27 ` Torsten Duwe
2019-12-01 23:49 ` 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=20191201234911.GC1998@sirena.org.uk \
--to=broonie@kernel.org \
--cc=duwe@lst.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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