All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Felipe Balbi <balbi@ti.com>
Cc: lgirdwood@gmail.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	airlied@linux.ie, robdclark@gmail.com, davidb@codeaurora.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] regulator: stub out devm_regulator_get_exclusive
Date: Fri, 24 Oct 2014 21:11:38 +0100	[thread overview]
Message-ID: <20141024201138.GL3729@sirena.org.uk> (raw)
In-Reply-To: <1414178111-19525-1-git-send-email-balbi@ti.com>

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

On Fri, Oct 24, 2014 at 02:15:11PM -0500, Felipe Balbi wrote:
> If we don't stup that call out, we will have
> build failures for any drivers using that function
> when .config happens to have CONFIG_REGULATOR=n.
> 
> One such case below, found with randconfig
> 
> drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c: In function ‘mdp4_kms_init’:
> drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c:384:2: error: implicit declaration \

As previously and repeatedly reported the regulator usage in this driver
appears extremely problematic, among these problems is that it almost
certainly has no sensible reason to be using regulator_get_exclusive()
or any variant of it.  Sadly every time it's been raised with the video
people they've completely ignored the mail so here we are.

Right now not having the stub seems to only be affecting buggy users
(which given the use cases for _exclusive() isn't *that* surprising) so
I'm more inclined to leave this there in the hope that the users get
fixed or we can at least get some sort of dialogue with the relevant
maintainers.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2014-10-24 20:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 19:15 [PATCH] regulator: stub out devm_regulator_get_exclusive Felipe Balbi
2014-10-24 19:15 ` Felipe Balbi
2014-10-24 19:20 ` Felipe Balbi
2014-10-24 19:20   ` Felipe Balbi
2014-10-24 20:11 ` Mark Brown [this message]
2014-10-24 20:18   ` Felipe Balbi
2014-10-24 20:18     ` Felipe Balbi
2014-10-24 20:58     ` Mark Brown
2014-10-24 20:36   ` Rob Clark
2014-10-24 20:36     ` Rob Clark
2014-10-24 21:18     ` Mark Brown
2014-10-24 21:57       ` Rob Clark
2014-10-24 21:57         ` Rob Clark
2014-10-25  9:46         ` Mark Brown
2014-10-25  9:46           ` 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=20141024201138.GL3729@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=airlied@linux.ie \
    --cc=balbi@ti.com \
    --cc=davidb@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@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.