linux-kernel - Re: [PATCH] power: bq27xxx_battery: Reorganize I2C into a module

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]

Date:	Mon, 23 Nov 2015 11:09:50 -0600
From:	"Andrew F. Davis" <afd@...com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Pali Rohár <pali.rohar@...il.com>,
	Sebastian Reichel <sre@...nel.org>,
	Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
	David Woodhouse <dwmw2@...radead.org>,
	Andreas Dannenberg <dannenberg@...com>,
	<linux-pm@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] power: bq27xxx_battery: Reorganize I2C into a module

On 11/23/2015 10:57 AM, Arnd Bergmann wrote:
> On Monday 23 November 2015 10:53:51 Andrew F. Davis wrote:
>> Separate out I2C functionality into a module. This fixes several small
>> issues and simplifies the driver initialization.
>>
>> Signed-off-by: Andrew F. Davis <afd@...com>
>
> That looks good to me overall, it should help with the randconfig
> warnings I've been seeing and makes the driver structured more logically.
>
> The one part I wonder about is whether the platform_driver portion
> should also be split out into a separate module in the same way.
>
> 	Arnd
>

I think it should, I'm just waiting until I can find some time to
bring up regmap for 1wire, then I can really clean things up and
move the platform stuff (which is really the 1wire interface) out
more cleanly, all I'll need to do then is just pass a regmap handle
to the core from the interface modules.

But that's all a project for another day :)
--
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/