Linux I2C development
 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,
	Peter Rosin <peda@axentia.se>
Subject: [PULL REQUEST] i2c for 4.13
Date: Fri, 25 Aug 2017 16:30:58 +0200	[thread overview]
Message-ID: <20170825143054.vguk564qjnrhv7hf@ninjato> (raw)

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

Linus,

I2C has some bugfixes for you: mainly Jarkko fixed up a few things in
the designware driver regarding the new slave mode. But Ulf also fixed a
long-standing and now agreed suspend problem. Plus, some simple stuff
which nonetheless needs fixing.

Please pull.

Thanks,

   Wolfram


The following changes since commit ef954844c7ace62f773f4f23e28d2d915adc419f:

  Linux 4.13-rc5 (2017-08-13 16:01:32 -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 2a86cdd2e7d3c75580f41f89f9b9211e225573cc:

  i2c: designware: Fix runtime PM for I2C slave mode (2017-08-17 17:55:29 +0200)

----------------------------------------------------------------
Anton Vasilyev (1):
      i2c: simtec: use release_mem_region instead of release_resource

Brendan Higgins (1):
      i2c: aspeed: fixed potential null pointer dereference

Jarkko Nikula (4):
      i2c: designware: Fix oops from i2c_dw_irq_handler_slave
      i2c: designware: Fix standard mode speed when configuring the slave mode
      i2c: designware: Remove needless pm_runtime_put_noidle() call
      i2c: designware: Fix runtime PM for I2C slave mode

Javier Martinez Canillas (1):
      i2c: core: Make comment about I2C table requirement to reflect the code

Ulf Hansson (1):
      i2c: designware: Fix system suspend


with much appreciated quality assurance from
----------------------------------------------------------------
Jarkko Nikula (1):
      (Test) i2c: designware: Fix system suspend

John Stultz (1):
      (Test) i2c: designware: Fix system suspend

Mika Westerberg (1):
      (Rev.) i2c: designware: Fix system suspend

 drivers/i2c/busses/i2c-aspeed.c             |  5 +++--
 drivers/i2c/busses/i2c-designware-platdrv.c | 17 +++++++++++++----
 drivers/i2c/busses/i2c-designware-slave.c   |  6 ++++--
 drivers/i2c/busses/i2c-simtec.c             |  6 ++----
 drivers/i2c/i2c-core-base.c                 |  4 ++--
 5 files changed, 24 insertions(+), 14 deletions(-)

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

             reply	other threads:[~2017-08-25 14:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 14:30 Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-09-01 21:40 [PULL REQUEST] i2c for 4.13 Wolfram Sang
2017-08-09 19:29 Wolfram Sang
2017-07-12 15:49 Wolfram Sang
2017-07-12 15:54 ` Wolfram Sang
2017-07-12 17:16 ` Linus Torvalds
2017-07-13  7:56   ` Uwe Kleine-König
2017-07-13 20:57     ` Peter Rosin
2017-07-13 21:05       ` Linus Torvalds
2017-07-13 21:41         ` Peter Rosin
2017-07-13 10:03   ` Wolfram Sang
2017-07-13 10:50     ` 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=20170825143054.vguk564qjnrhv7hf@ninjato \
    --to=wsa@the-dreams.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    --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