Tony,

> -----Original Message-----
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Wednesday, February 17, 2010 12:33 AM
> To: Shilimkar, Santosh
> Cc: Ben Dooks; Samuel Ortiz; Kevin Hilman; Paul Walmsley; 
> l...@slimlogic.co.uk; linux-
> o...@vger.kernel.org
> Subject: Re: [PATCH 0/24] omap4 for 2.6.34
> 
> Hi,
> 
> * Shilimkar, Santosh <santosh.shilim...@ti.com> [100216 07:33]:
> > Tony,
> > Here are some patches towards upcoming 34 merge window. They are generated 
> > against
> > linux-omap master as you suggested.
> >
> > I am also copying Ben, Samuel, Liam, Paul and Kevin since some of the 
> > changes
> > are in mfd, regulator, i2c and clocks.
> 
> Thanks. Can you please split this into several smaller sets?
> 
> 1. Core omap changes done against linux-omap master branch
>    Send to linux-omap list with linux-arm-kernel Cc'd.
ok 
> 2. Clock framework dummy_ck changes done against linux-omap master branch.
>    This should leave out most of the driver changes in your series.
>    Send to linux-omap list with linux-arm-kernel Cc'd.
Will do. Some clock node names are changed and since we do clk_get based on 
clock node
names, such drivers need to change. 
> 3. I2C changes against done against 2.6.33-rc8 + "Add support for 16-bit 
> registers"
>    Send to Ben and i2c list with linux-omap list Cc'd.
ok
> 4. MFD changes done against 2.6.33-rc8
>    Send to Samuel with linux-omap list Cc'd.
Sounds good.
I sent this series just to ensure that we all are aligned on
dependancies and also just to highlight that all of these 
should get merged together.

Thanks for feedback.

Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to