From: Anton Vorontsov on
On Wed, Jun 02, 2010 at 09:12:29PM +0200, Lars-Peter Clausen wrote:
> This patch adds support for the battery voltage measurement part of the JZ4740
> ADC unit.
>
> Signed-off-by: Lars-Peter Clausen <lars(a)metafoo.de>
> Cc: Anton Vorontsov <cbouatmailru(a)gmail.com>
> ---

Looks good. I see this is an RFC. Do you want me to apply it
or there's a newer version to be submitted?

Thanks,

--
Anton Vorontsov
email: cbouatmailru(a)gmail.com
irc://irc.freenode.net/bd2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Lars-Peter Clausen on
Anton Vorontsov wrote:
> On Wed, Jun 02, 2010 at 09:12:29PM +0200, Lars-Peter Clausen wrote:
>
>> This patch adds support for the battery voltage measurement part of the JZ4740
>> ADC unit.
>>
>> Signed-off-by: Lars-Peter Clausen <lars(a)metafoo.de>
>> Cc: Anton Vorontsov <cbouatmailru(a)gmail.com>
>> ---
>>
>
> Looks good. I see this is an RFC. Do you want me to apply it
> or there's a newer version to be submitted?
>
> Thanks,
>
>
Hi. Thanks for taking a look at it.
I'll send a new series which has some minor cleanups for the battery
driver soon.

- Lars
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Ralf Baechle on
On Mon, Jun 14, 2010 at 07:51:08PM +0400, Anton Vorontsov wrote:

> On Wed, Jun 02, 2010 at 09:12:29PM +0200, Lars-Peter Clausen wrote:
> > This patch adds support for the battery voltage measurement part of the JZ4740
> > ADC unit.
> >
> > Signed-off-by: Lars-Peter Clausen <lars(a)metafoo.de>
> > Cc: Anton Vorontsov <cbouatmailru(a)gmail.com>
> > ---
>
> Looks good. I see this is an RFC. Do you want me to apply it
> or there's a newer version to be submitted?

To allow for reasonable testing while this patchset is getting integrated
I suggest I apply all the patches that were acked by the respective
maintainers to the MIPS tree, feed them to -next for testing and once
that phase is complete send the whole thing to Linus.

Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Mark Brown on
On Tue, Jun 15, 2010 at 06:34:32PM +0100, Ralf Baechle wrote:
> On Mon, Jun 14, 2010 at 07:51:08PM +0400, Anton Vorontsov wrote:

> > Looks good. I see this is an RFC. Do you want me to apply it
> > or there's a newer version to be submitted?

> To allow for reasonable testing while this patchset is getting integrated
> I suggest I apply all the patches that were acked by the respective
> maintainers to the MIPS tree, feed them to -next for testing and once
> that phase is complete send the whole thing to Linus.

Due to major pending changes in the audio subsystem at least the audio
subsystem changes will have merge issues in -next from that. To avoid
these I suggest putting the audio changes on a branch which can be
pulled into both trees.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Lars-Peter Clausen on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi
Mark Brown wrote:
> On Tue, Jun 15, 2010 at 06:34:32PM +0100, Ralf Baechle wrote:
>> To allow for reasonable testing while this patchset is getting
>> integrated I suggest I apply all the patches that were acked by
>> the respective maintainers to the MIPS tree, feed them to -next
>> for testing and once that phase is complete send the whole thing
>> to Linus.
>
> Due to major pending changes in the audio subsystem at least the
> audio subsystem changes will have merge issues in -next from that.
> To avoid these I suggest putting the audio changes on a branch
> which can be pulled into both trees.
In my opinion the ASoC drivers can go through the ASoC tree. The core
patches will build without the ASoC patches and the ASoC drivers wont
be selectable without the core patches. Thus we wont see any build
failures due to merging both parts individually. And given that there
will be some changes required when the multi-component branch is
merged it will simplify things if the patches only go through one tree.
I've talked to Ralf and he said he is ok with it.

- - Lars
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkwcPhcACgkQBX4mSR26RiOJSgCfScB+QFGTbzAqfbmvAVntvqDb
Xv8An1672tE+ZkLqBBYuhU18AEZdVmkT
=n6/A
-----END PGP SIGNATURE-----

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/