linux-kernel - Re: [PATCH v1 02/10] i2c: core: Have clients point to their firmware nodes

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: <CAAObsKD557c5ssAYUqa=azCs05=o5CA++-sFOBx=063Zwev2dQ@mail.gmail.com>
Date:	Thu, 6 Aug 2015 16:17:28 +0200
From:	Tomeu Vizoso <tomeu.vizoso@...labora.com>
To:	Wolfram Sang <wsa@...-dreams.de>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Mark Brown <broonie@...nel.org>, linux-i2c@...r.kernel.org
Subject: Re: [PATCH v1 02/10] i2c: core: Have clients point to their firmware nodes

On 31 July 2015 at 12:36, Wolfram Sang <wsa@...-dreams.de> wrote:
> On Tue, Jun 30, 2015 at 04:55:00PM +0200, Tomeu Vizoso wrote:
>> This is needed by platform-independent code that needs to do something
>> with devices based on the data provided by the firmware.
>>
>> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@...labora.com>
>
> Dunno the status of this series, but the i2c change is trivial enough.
> So in case, the rest is accepted:
>
> Acked-by: Wolfram Sang <wsa@...-dreams.de>

Currently my series is moving away from fwnode because the current
approach is very much dependent on the firmware, but I think this fix
is worth in its own because someone else will find this problem sooner
or later.

Regards,

Tomeu
--
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/