linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: regulator-core has_full_constraints set too late for dt using boards ?
Date: Thu, 12 Dec 2013 13:19:39 +0100	[thread overview]
Message-ID: <52A9A9DB.5050102@redhat.com> (raw)
In-Reply-To: <20131212104208.GG11044@sirena.org.uk>

Hi,

On 12/12/2013 11:42 AM, Mark Brown wrote:
> On Thu, Dec 12, 2013 at 11:14:10AM +0100, Hans de Goede wrote:
>> On 12/11/2013 05:02 PM, Mark Brown wrote:
>
>>> Please look at the current code, that's not how this works any more.
>
>> More current then 3.13-rc3 ? Because that is what I've been looking at.
>
> Yes, -next.  It'll be going to Linus probably this week.
>
>> I could be completely wrong of course. Either way could you give a few
>> hints as to how my interpretation of how this works is wrong ?
>
> It's correct for the code you've been looking at but has since been
> changed.  Please look at the changes in -next, you should generally
> check -next for the current state of things.

Ah yes, I see, thanks for clarifying this.

Note my patch to not do a dev_err when no regulator is found for
regulator_get_optional still is needed in -next.

Thanks & Regards,

Hans

  reply	other threads:[~2013-12-12 12:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 15:43 regulator-core has_full_constraints set too late for dt using boards ? Hans de Goede
2013-12-11 16:02 ` Mark Brown
2013-12-12 10:14   ` Hans de Goede
2013-12-12 10:42     ` Mark Brown
2013-12-12 12:19       ` Hans de Goede [this message]
2013-12-12 12:23         ` Mark Brown
2013-12-12 13:05           ` Hans de Goede
2013-12-12 13:16             ` 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=52A9A9DB.5050102@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).