All of lore.kernel.org
 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.9
Date: Thu, 27 Oct 2016 15:08:42 +0200	[thread overview]
Message-ID: <20161027130838.GA2462@tetsubishi> (raw)

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

Linus,

I2C has some driver bugfixes, module autoload fixes, and driver
enablement on some architectures for you.

Please pull.

Thanks,

   Wolfram


The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69:

  Linux 4.9-rc2 (2016-10-23 17:10:14 -0700)

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 533169d164c6b4c8571d0d48779f6ff6be593d72:

  i2c: imx: defer probe if bus recovery GPIOs are not ready (2016-10-25 12:15:00 +0200)

----------------------------------------------------------------
David Wu (1):
      i2c: rk3x: Give the tuning value 0 during rk3x_i2c_v0_calc_timings

Greg Ungerer (1):
      i2c: allow configuration of imx driver for ColdFire architecture

Hoan Tran (1):
      i2c: xgene: Avoid dma_buffer overrun

Jarkko Nikula (1):
      i2c: designware: Avoid aborted transfers with fast reacting I2C slaves

Javier Martinez Canillas (4):
      i2c: jz4780: Fix module autoload
      i2c: xlp9xx: Fix module autoload
      i2c: xlr: Fix module autoload for OF registration
      i2c: digicolor: Fix module autoload

Jean Delvare (1):
      i2c: i801: Fix I2C Block Read on 8-Series/C220 and later

Ralf Ramsauer (1):
      i2c: mark device nodes only in case of successful instantiation

Ruqiang Ju (1):
      i2c: hix5hd2: allow build with ARCH_HISI

Stefan Agner (1):
      i2c: imx: defer probe if bus recovery GPIOs are not ready

 drivers/i2c/busses/Kconfig               | 12 ++++++------
 drivers/i2c/busses/i2c-designware-core.c | 17 ++++++++++++++---
 drivers/i2c/busses/i2c-digicolor.c       |  1 +
 drivers/i2c/busses/i2c-i801.c            | 16 +++++++++++++---
 drivers/i2c/busses/i2c-imx.c             | 11 +++++++----
 drivers/i2c/busses/i2c-jz4780.c          |  1 +
 drivers/i2c/busses/i2c-rk3x.c            |  2 ++
 drivers/i2c/busses/i2c-xgene-slimpro.c   |  2 +-
 drivers/i2c/busses/i2c-xlp9xx.c          |  1 +
 drivers/i2c/busses/i2c-xlr.c             |  1 +
 drivers/i2c/i2c-core.c                   | 11 ++++++++++-
 11 files changed, 57 insertions(+), 18 deletions(-)

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

             reply	other threads:[~2016-10-27 14:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27 13:08 Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-12-02 13:21 [PULL REQUEST] i2c for 4.9 Wolfram Sang
2016-11-26 22:12 Wolfram Sang
2016-11-19 21:31 Wolfram Sang
2016-11-05 22:16 Wolfram Sang
2016-10-14 11:37 Wolfram Sang
2016-10-07  9:32 Wolfram Sang
2016-10-07 10:59 ` Bartosz Golaszewski
2016-10-07 20:37   ` Wolfram Sang
2016-10-07 21:17 ` Linus Torvalds
2016-10-08 19:42   ` 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=20161027130838.GA2462@tetsubishi \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.