linux-kernel - Re: [PATCH 15/27] regulator: fan53555: Export I2C module alias information

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: <20150803154413.GT20873@sirena.org.uk>
Date:	Mon, 3 Aug 2015 16:44:13 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Javier Martinez Canillas <javier@....samsung.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 15/27] regulator: fan53555: Export I2C module alias
 information

On Mon, Aug 03, 2015 at 01:43:38PM +0200, Paul Bolle wrote:

> That being said, before this patch the fan53555 module contained these
> aliases:
>     alias:          of:N*T*Csilergy,syr828*
>     alias:          of:N*T*Csilergy,syr827*
>     alias:          of:N*T*Cfcs,fan53555*

> While this patch ad these two aliases:
>     alias:          i2c:syr82x
>     alias:          i2c:fan53555

> Now I don't have an "of" or "i2c" capable machine at hand, which makes
> it a bit hard to figure out how all of this is supposed to fit together.
> But I'm guessing that parsing a device tree blob that contains strings
> like

The DT and I2C namespaces are intended to be completely unrelated to
each other, both are needed in different systems.

> But neither the string "fan53555" nor the string "syr82x" generate
> interesting hits in current linux-next. Are these strings perhaps only
> used in out of tree device tree source files?

Please stop going on about this, as has previously been discussed we do
*NOT* require board files, device tree files or any other kind of board
description to be included in mainline.  There is no expectation that we
will see anything instantiating any particular device included in the
kernel source, and in some cases such as ACPI this never happens at all.

I'm not sure how this can be made any clearer.

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