linux-kernel - Re: [PATCH] regulator: Provide a check for dummy regulator

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJe_ZhcfcTGjmy-n1hrVjvQ-8+Si4VAWaCf18cpap3NW5b+M=g@mail.gmail.com>
Date:	Sat, 21 Apr 2012 00:41:18 +0530
From:	Jassi Brar <jaswinder.singh@...aro.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org, lrg@...com
Subject: Re: [PATCH] regulator: Provide a check for dummy regulator

On 21 April 2012 00:18, Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:

Going for the closure.
I have a last nail. Don't know whose coffin is it for ;)

>
> In any case, the solution is very clear - just do proper regulator
> support and turn off dummy regulators and everything is fine.
>
You earlier said there are always going to be 'new' platforms that would
need dummy enabled.
Now just imagine if one of those platforms happen to share the consumer
due to which you suggest disabling the dummy (omap_hsmmc in this case).
If we re-enable dummy, then your's isn't really a solution.
If we require that platform to come with full compliance, why can't we
ask every platform to do the same?

Thanks,
-Jassi
--
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/