linux-mips
[Top] [All Lists]

Re: [RFC][PATCH 23/26] power: Add JZ4740 battery driver.

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [RFC][PATCH 23/26] power: Add JZ4740 battery driver.
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
Date: Wed, 16 Jun 2010 13:20:43 +0100
Cc: Anton Vorontsov <cbouatmailru@gmail.com>, Lars-Peter Clausen <lars@metafoo.de>, linux-mips@linux-mips.org, linux-kernel@vger.kernel.org, lrg@slimlogic.co.uk
In-reply-to: <20100615173432.GA27904@linux-mips.org>
References: <1275505397-16758-1-git-send-email-lars@metafoo.de> <1275505950-17334-7-git-send-email-lars@metafoo.de> <20100614155108.GA30552@oksana.dev.rtsoft.ru> <20100615173432.GA27904@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.18 (2008-05-17)
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.

<Prev in Thread] Current Thread [Next in Thread>