All of lore.kernel.org
 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 14:05:14 +0100	[thread overview]
Message-ID: <52A9B48A.8040601@redhat.com> (raw)
In-Reply-To: <20131212122347.GK11044@sirena.org.uk>

Hi,

On 12/12/2013 01:23 PM, Mark Brown wrote:
> On Thu, Dec 12, 2013 at 01:19:39PM +0100, Hans de Goede wrote:
>
>> Note my patch to not do a dev_err when no regulator is found for
>> regulator_get_optional still is needed in -next.
>
> It's sitting in my review queue, it's not very well described so it's
> not clear that you've selected the correct criteria and I need to find
> time to actually look at it properly.

I did not want to add a third boolean parameter to indicate
_regulator_get() was being called from regulator_get_optional.

Since regulator_get_optional is the only one calling
_regulator_get() with both allow_dummy and exclusive set to
false I've added the following condition to printing the
error:

	if (!(!allow_dummy && !exclusive))

Simplified to:

	if (allow_dummy || exclusive)

Which means that it will get printed in all cases it would
get printed previously, except when called from
regulator_get_optional.

Alternatively a third "optional" boolean parameter could
get added to _regulator_get() and the test for printing the
error could become:

	if (!optional)

Let me know if you would prefer doing things that way and
I'll respin the patch.

Thanks & Regards,

Hans

  reply	other threads:[~2013-12-12 13:05 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
2013-12-12 12:23         ` Mark Brown
2013-12-12 13:05           ` Hans de Goede [this message]
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=52A9B48A.8040601@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 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.