linux-kernel - Re: [PATCH V3 2/3] regulator: dt: regulator match by regulator-compatible

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>] [day] [month] [year] [list]

Message-ID: <20120621223632.GA4037@opensource.wolfsonmicro.com>
Date:	Thu, 21 Jun 2012 23:36:33 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Mitch Bradley <wmb@...mworks.com>
Cc:	Arnd Bergmann <arnd@...db.de>, devicetree-discuss@...ts.ozlabs.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	rob.herring@...xeda.com, Laxman Dewangan <ldewangan@...dia.com>,
	lee.jones@...aro.org, lrg@...com
Subject: Re: [PATCH V3 2/3] regulator: dt: regulator match by
 regulator-compatible

On Thu, Jun 21, 2012 at 11:53:41AM -1000, Mitch Bradley wrote:

Whatever mail program you're using appears to be generating HTML mails
and isn't doing an awesome job at formatting them, the plain text
version is mangled too with most peculiar word wrapping which is quite
hard to read.  I've reflowed.

> On 6/21/2012 9:45 AM, Mark Brown wrote:
> >On Thu, Jun 21, 2012 at 05:17:45PM +0000, Arnd Bergmann wrote:
> >>On Thursday 21 June 2012, Mark Brown wrote:

> >>>I'm not that big a fan of moving all the data into device tree as it
> >>>means that you need even more parsing code and you need to update the
> >>>device trees for every board out there every time you want to add
> >>>support for a new feature which doesn't seem like a win.

> Maybe I'm missing something, but in general it's not necessary to
> update old device trees to support new features.  The trick is to
> define a new property that describes the new possibility.  Absence of
> that property implies that the default - the thing that used to happen
> across the board, before the feature existed - applies.

Which is not a success in terms of deploying the new support, or indeed
in terms of deploying bugfixes.  It increases the overall complexity of
the system and I'm having a hard time getting at all excited about any
benefits.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)