linux-kernel - Re: [PATCHv2 3/3] regmap: add DT endianness binding support.

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: <20140414210713.GA12304@sirena.org.uk>
Date:	Mon, 14 Apr 2014 22:07:13 +0100
From:	Mark Brown <broonie@...nel.org>
To:	"Li.Xiubo@...escale.com" <Li.Xiubo@...escale.com>
Cc:	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCHv2 3/3] regmap: add DT endianness binding support.

On Thu, Apr 03, 2014 at 05:26:57AM +0000, Li.Xiubo@...escale.com wrote:

> > Actually, if we're going to be doing this for all devices then we
> > probably need to namespace the properties too.  Not sure what to do for
> > a prefix though.  One for the DT folks.

> How about using one prefix string of each regmap bus?
> Such as:
> Prefix 'regmap-mmio' for regmap-mmio,
> Prefix 'regmap-i2c' for regmap-i2c,
> Precix 'regmap-spi' for regmap-spi
> ...

> Or just using the same prefix 'regmap' for all of them ?

I don't see any point in defining separate per bus properties so just
one prefix.

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