| Message ID | 871uwbhdoj.fsf@ti.com |
|---|---|
| State | New |
| Headers | show |
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? Since master.kernel.org is still down, I pushed a (backup) copy of these branches to my gitorious repo[1]. It should pull cleanly into what you've already pulled since this branch is based on my for_3.2/i2c-fixes which you've already pulled. Thanks, Kevin [1] git://gitorious.org/khilman/linux-omap-pm.git
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? > > Since master.kernel.org is still down, I pushed a (backup) copy of these > branches to my gitorious repo[1]. It should pull cleanly into what > you've already pulled since this branch is based on my for_3.2/i2c-fixes > which you've already pulled. > > Thanks, > > Kevin > > > [1] git://gitorious.org/khilman/linux-omap-pm.git
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? > > Since master.kernel.org is still down, I pushed a (backup) copy of these > branches to my gitorious repo[1]. It should pull cleanly into what > you've already pulled since this branch is based on my for_3.2/i2c-fixes > which you've already pulled. > > Thanks, > > Kevin > > > [1] git://gitorious.org/khilman/linux-omap-pm.git > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html
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?
Ben Dooks <ben-i2c@fluff.org> 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. Kevin [1] git://github.com/khilman/linux-omap-pm.git for_3.2/i2c-cleanup
On Thu, Oct 6, 2011 at 12:11 AM, Kevin Hilman <khilman@ti.com> wrote: > Ben Dooks <ben-i2c@fluff.org> 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,
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. Thanks, Kevin The following changes since commit f3cb1e11c4e54f4dc7e60f9513d43ffa0bbebc25: Revert "i2c-omap: fix static suspend vs. runtime suspend" (2011-08-23 10:51:58 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.2/i2c-cleanup Kevin Hilman (3): I2C: OMAP: remove unneccesary use of pdev I2C: OMAP: remove dev->idle, use usage counting provided by runtime PM I2C: OMAP: remove unused function pointers from pdata drivers/i2c/busses/i2c-omap.c | 77 +++++++++++++++++++++++----------------- include/linux/i2c-omap.h | 3 -- 2 files changed, 44 insertions(+), 36 deletions(-)