[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOMZO5ATGZB=PZzgK71mJyf10o1WvJuYQtxsiOjkMB3r9WqQ=A@mail.gmail.com>
Date: Mon, 24 Feb 2014 23:18:08 -0300
From: Fabio Estevam <festevam@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Markus Pargmann <mpa@...gutronix.de>,
Sascha Hauer <kernel@...gutronix.de>,
Liam Girdwood <lgirdwood@...il.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/2] regulator: core: Fix ops->enable/disable usage
On Mon, Feb 24, 2014 at 10:34 PM, Mark Brown <broonie@...nel.org> wrote:
> On Mon, Feb 24, 2014 at 09:50:58PM +0100, Markus Pargmann wrote:
>
>> The only situation where this returns -EINVAL is a dummy regulator that
>> is not always_on. As it doesn't make sense to have a dummy regulator
>> that is not always_on, I will add a check for exactly this situation to
>> the regulator_register function and drop the "return -EINVAL" above.
>
> I've squashed the following fix in today:
Thanks. This fixes the issue.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists