On Thu, Oct 6, 2011 at 12:11 AM, Kevin Hilman <khilman@xxxxxx> wrote: > Ben Dooks <ben-i2c@xxxxxxxxx> writes: > >> On Mon, Sep 26, 2011 at 03:30:50PM -0700, Kevin Hilman wrote: >>> ping >>> >>> On 09/06/2011 03:31 PM, Kevin Hilman wrote: >>> >Hi Ben, >>> > >>> >On 08/23/2011 05:10 PM, Kevin Hilman wrote: >>> >>Ben, >>> >> >>> >>Here's one more I2C cleanup series for v3.2. >>> >> >>> >>It applies on top of my for_3.2/i2c-fixes branch just submitted. >>> >> >>> >>Please pull into your tree for linux-next. >>> > >>> >I see you pulled the other two, can you pull this one as well? >> >> I've tried, but it seems to note that everything is up to date. >> >> Is this a suitable branch to pull onto latest so I can reset >> my next tree? > > Yes. > > The i2c-cleanup branch[1] is based on top of the previous two (i2c-andy > and i2c-fixes) so if you reset your next-i2c branch and just pull > i2c-cleanup, you'll get all three. BTW: The patch[1] is a fix patch, which fix the OOPS[2] during system resume, so should CC -stable tree. [1], I2C: OMAP: remove dev->idle, use usage counting provided by runtime PM [2], http://marc.info/?l=linux-omap&m=131658936429671&w=2 thanks, -- Ming Lei -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
