linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Ben Dooks <ben-linux@fluff.org>, Tony Lindgren <tony@atomide.com>
Cc: linux-i2c@vger.kernel.org,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] I2C: OMAP: misc. cleanup for v3.2
Date: Tue, 23 Aug 2011 17:10:36 -0700	[thread overview]
Message-ID: <871uwbhdoj.fsf@ti.com> (raw)

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(-)

             reply	other threads:[~2011-08-24  0:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  0:10 Kevin Hilman [this message]
     [not found] ` <871uwbhdoj.fsf-l0cyMroinI0@public.gmane.org>
2011-09-06 22:31   ` [GIT PULL] I2C: OMAP: misc. cleanup for v3.2 Kevin Hilman
     [not found]     ` <4E669F36.2070008-l0cyMroinI0@public.gmane.org>
2011-09-12 17:39       ` Kevin Hilman
2011-09-26 22:30       ` Kevin Hilman
     [not found]         ` <4E80FD1A.5040006-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2011-10-04 21:08           ` Ben Dooks
     [not found]             ` <20111004210832.GC13323-RazCHl0VsYgkUSuvROHNpA@public.gmane.org>
2011-10-05 16:11               ` Kevin Hilman
2011-10-09 11:35                 ` Ming Lei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871uwbhdoj.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=ben-linux@fluff.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).