linux-kernel - Re: [PATCH V3 0/7] PCF50633 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: <20090112144434.eeb1640d.akpm@linux-foundation.org>
Date:	Mon, 12 Jan 2009 14:44:34 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Balaji Rao <balajirrao@...nmoko.org>
Cc:	linux-kernel@...r.kernel.org, sameo@...nedhand.com
Subject: Re: [PATCH V3 0/7] PCF50633 support

On Mon, 05 Jan 2009 23:42:42 +0530
Balaji Rao <balajirrao@...nmoko.org> wrote:

> The following series implements support for NXP PCF50633. It's basically
> an I2C device with 9 regulators, an ADC, a PMIC, a Battery Charger
> and a RTC.
> 
> This chip is used in Openmoko Neo Freerunner mobile phone.
> 
> The specs are open and are available at 
> http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633DS_02.pdf
> 
> ---
> Balaji Rao (7):
>       mfd: PCF50633 core driver
>       mfd: PCF50633 adc driver
>       mfd: PCF50633 gpio support
>       rtc: PCF50633 rtc driver
>       power_supply: PCF50633 battery charger driver
>       input: PCF50633 input driver
>       regulator: PCF50633 pmic driver

You have patches here which should strictly be merged by various
different subsystem trees.  That gets tricky because presumably there
are dependencies.

What _are_ the dependencies here?  Do patches 2-7 depend upon #1, perhaps?

If so, then one approach would be to merge the first patch into
mainline now then trickle the rest out into subsystem trees.

Or, with suitable acks, I can merge the lot.  Perhaps into 2.6.29..

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