From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jean Delvare <khali@linux-fr.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] regulator: core: Correct default return value for full constraints
Date: Mon, 3 Feb 2014 17:31:04 +0000 [thread overview]
Message-ID: <20140203173104.GF22609@sirena.org.uk> (raw)
In-Reply-To: <20140203165210.GB30754@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
On Mon, Feb 03, 2014 at 08:52:10AM -0800, Guenter Roeck wrote:
> On Mon, Feb 03, 2014 at 03:41:09PM +0000, Mark Brown wrote:
> > It's on a fixes tag so it'll go in next time I send stuff to Linus,
> > it'll go next time I send something to him. That's usually about once
> > per release. Especially if things are tagged for stable I like to try
> > to avoid sending them too quickly unless they're build breaks or
> > similar.
> We still have the lm90 driver failing in 13.3 for non-DT platforms.
> One should think that this has some level of importance. If a driver
> doesn't build or doesn't work makes little difference for the user,
> after all.
On the other hand it's a hardware monitoring driver which nobody managed
to notice problems with for pretty much an entire release cycle and a
fix in the core regulator lookup code which has the ability to break
boot prior to the console coming up if it goes wrong. An extra week is
not going to be the end of the world here but helps ensure better
exposure of what hits stable.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-02-03 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 18:07 Mark Brown
2014-02-03 9:41 ` Jean Delvare
2014-02-03 11:02 ` Mark Brown
2014-02-03 14:35 ` Jean Delvare
2014-02-03 15:41 ` Mark Brown
2014-02-03 16:52 ` Guenter Roeck
2014-02-03 17:31 ` 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=20140203173104.GF22609@sirena.org.uk \
--to=broonie@kernel.org \
--cc=khali@linux-fr.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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®