regmap tree for -next

regmap tree for -next

[Mark Brown]

Hi Stephen,

Please consider including the tree at:

   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

in -next, providing Greg is happy with me doing this (the code currently
sits under drivers/base).  I'm using this tree for development of a
generic register map API for I2C and SPI type devices, factoring out a
bunch of widely duplicated code and hopefully also providing a basis for
further code sharing.

Thanks,
Mark

Re: regmap tree for -next

[Greg KH]

On Sat, Jul 09, 2011 at 01:53:17PM +0900, Mark Brown wrote:
> Hi Stephen,
> 
> Please consider including the tree at:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
> 
> in -next, providing Greg is happy with me doing this (the code currently
> sits under drivers/base).  I'm using this tree for development of a
> generic register map API for I2C and SPI type devices, factoring out a
> bunch of widely duplicated code and hopefully also providing a basis for
> further code sharing.

No objection from me.

thanks,

greg k-h

Re: regmap tree for -next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]

Hi Mark,

On Sat, 9 Jul 2011 13:53:17 +0900 Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
>
> Please consider including the tree at:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
> 
> in -next, providing Greg is happy with me doing this (the code currently
> sits under drivers/base).  I'm using this tree for development of a
> generic register map API for I2C and SPI type devices, factoring out a
> bunch of widely duplicated code and hopefully also providing a basis for
> further code sharing.

Given Greg's blessing, I will include this tree in the next linux-next
release.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]