linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PULL REQUEST] i2c for 4.5
Date: Sat, 20 Feb 2016 23:12:36 +0100	[thread overview]
Message-ID: <20160220221232.GA1808@katana> (raw)

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

Linus,

some bugfixes from I2C for you:

A fix for a RuntimePM regression with OMAP, a fix to enable TCO for
Lewisburg platforms, and a typo fix while we are here.

Please pull. Thanks,

   Wolfram


The following changes since commit 388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95:

  Linux 4.5-rc3 (2016-02-07 15:38:30 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-current

for you to fetch changes up to 1a1503c5396eb7f2edf4b8ef6067853014478c0c:

  i2c: i801: Adding Intel Lewisburg support for iTCO (2016-02-18 13:18:48 +0100)

----------------------------------------------------------------
Alexandra Yates (1):
      i2c: i801: Adding Intel Lewisburg support for iTCO

Masahiro Yamada (1):
      i2c: uniphier: fix typos in error messages

Tony Lindgren (1):
      i2c: omap: Fix PM regression with deferred probe for pm_runtime_reinit

 drivers/i2c/busses/i2c-i801.c       | 2 ++
 drivers/i2c/busses/i2c-omap.c       | 4 +++-
 drivers/i2c/busses/i2c-uniphier-f.c | 2 +-
 drivers/i2c/busses/i2c-uniphier.c   | 2 +-
 4 files changed, 7 insertions(+), 3 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-02-20 22:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20 22:12 Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-06 11:52 [PULL REQUEST] i2c for 4.5 Wolfram Sang
2016-01-31  0:06 Wolfram Sang
2016-01-14 19:18 Wolfram Sang

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=20160220221232.GA1808@katana \
    --to=wsa@the-dreams.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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).