All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bjorn Andersson <bjorn.andersson@sonymobile.com>
Cc: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Hai Li <hali@codeaurora.org>, Rob Clark <robdclark@gmail.com>,
	Dave Airlie <airlied@linux.ie>
Subject: Re: linux-next: build failure after merge of the regulator tree
Date: Tue, 14 Apr 2015 11:22:41 +1000	[thread overview]
Message-ID: <20150414112241.3dbad71a@canb.auug.org.au> (raw)
In-Reply-To: <20150414010706.GB29061@sonymobile.com>

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

Hi Bjorn,

On Mon, 13 Apr 2015 18:07:06 -0700 Bjorn Andersson <bjorn.andersson@sonymobile.com> wrote:
>
> What Mark mean is basically that there shouldn't be any users of
> regulator_set_optimum_mode() for various reasons and we introduced
> regulator_set_load() to solve these, before any users popped up.
> 
> Unfortunately we weren't fast enough and people got some code in that
> uses the API that isn't implemented for any Qualcomm platform today...

Ah, OK.

> Your patch looks correct and should preferrably be added to the drm
> tree, or the last patch in my series that drops the API wrapper should
> be held back until rc1(?)

It needs to be sent to Linus as a merge fix when the drm tree is merged.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-04-14  1:22 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09  4:33 linux-next: build failure after merge of the regulator tree Stephen Rothwell
2015-04-09  9:35 ` Mark Brown
2015-04-13 23:44   ` Stephen Rothwell
2015-04-14  1:07     ` Bjorn Andersson
2015-04-14  1:22       ` Stephen Rothwell [this message]
2015-04-14  9:40         ` Mark Brown
2015-04-15  3:03           ` Dave Airlie
2015-04-09 15:00 ` Rob Clark
2015-04-09 23:49   ` drm-msm tree (Was: Re: linux-next: build failure after merge of the regulator tree) Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2022-07-07  3:01 linux-next: build failure after merge of the regulator tree Stephen Rothwell
2021-11-23  7:41 Stephen Rothwell
2021-11-23  8:33 ` Vaittinen, Matti
2021-11-23  9:26 ` Vaittinen, Matti
2021-11-23 14:17   ` Mark Brown
2021-10-22  1:53 Stephen Rothwell
2021-10-22 10:31 ` Alistair
2021-10-22 12:40   ` Mark Brown
2020-02-25 23:39 Stephen Rothwell
2019-09-03  4:26 Stephen Rothwell
2019-09-03  6:46 ` Bartosz Golaszewski
2019-08-29  3:57 Stephen Rothwell
2018-11-20  0:49 Stephen Rothwell
2018-11-20  0:56 ` Dmitry Osipenko
2017-02-01  2:42 Stephen Rothwell
2017-02-01 10:03 ` Mark Brown
2017-02-02 22:30   ` Stephen Rothwell
2017-02-03 11:31     ` Mark Brown
2015-03-10  2:44 Stephen Rothwell
2015-03-10 10:40 ` Mark Brown
2014-09-08  8:33 Stephen Rothwell
2014-09-09 22:39 ` Mark Brown
2014-09-10  2:33   ` Chris Zhong
2014-09-10 10:54     ` Mark Brown
2014-09-10  2:50   ` Doug Anderson
2014-08-17 20:41 Stephen Rothwell
2014-07-08  3:10 Stephen Rothwell
2014-05-27  4:41 Stephen Rothwell
2014-01-06  6:37 Stephen Rothwell
2013-07-01  4:18 Stephen Rothwell
2013-07-01  6:07 ` Kishon Vijay Abraham I
2013-07-01  6:07   ` Kishon Vijay Abraham I
2013-07-01  8:43   ` Mark Brown
2013-07-01  8:47     ` Kishon Vijay Abraham I
2013-07-01  8:47       ` Kishon Vijay Abraham I
2013-07-01  8:42 ` Mark Brown
2012-09-10  3:20 Stephen Rothwell
2012-06-21  3:27 Stephen Rothwell
2012-06-21  8:13 ` Kim, Milo
2012-06-21  8:20   ` Axel Lin
2012-06-21  8:42     ` Kim, Milo
2012-06-21  9:14     ` Mark Brown
2012-06-21 11:04     ` Stephen Rothwell
2012-06-21 11:04       ` Stephen Rothwell
2012-06-21 11:30       ` Mark Brown
2012-06-21 17:35       ` Andrew Morton
2012-06-21 17:35         ` Andrew Morton
2012-06-21  9:46   ` Mark Brown
2012-06-20  4:50 Stephen Rothwell
2012-06-20  4:55 ` Axel Lin
2012-06-20 15:33   ` Stephen Warren
2012-04-10  3:01 Stephen Rothwell
2011-11-24  3:10 Stephen Rothwell
2011-11-24  7:31 ` Rajendra Nayak

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=20150414112241.3dbad71a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=broonie@kernel.org \
    --cc=hali@codeaurora.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robdclark@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.