linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PULL REQUEST] i2c for 3.17
Date: Fri, 3 Oct 2014 23:10:58 +0200	[thread overview]
Message-ID: <20141003211053.GA2176@katana> (raw)

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

Linus,

here are two i2c driver bugfixes which would be nice to have in 3.17.

Thanks,

   Wolfram


The following changes since commit fe82dcec644244676d55a1384c958d5f67979adb:

  Linux 3.17-rc7 (2014-09-28 14:29:07 -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 86b59bbfae2a895aa26b3d15f31b1a705dbfede1:

  i2c: qup: Fix order of runtime pm initialization (2014-10-03 03:20:47 +0200)

----------------------------------------------------------------
Alexandru M Stan (1):
      i2c: rk3x: fix 0 length write transfers

Andy Gross (1):
      i2c: qup: Fix order of runtime pm initialization

 drivers/i2c/busses/i2c-qup.c  | 12 ++++++++----
 drivers/i2c/busses/i2c-rk3x.c |  2 +-
 2 files changed, 9 insertions(+), 5 deletions(-)

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

             reply	other threads:[~2014-10-03 21:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03 21:10 Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-25 18:41 [PULL REQUEST] i2c for 3.17 Wolfram Sang
2014-09-05 19:41 Wolfram Sang
2014-08-21  3:25 Wolfram Sang
2014-08-09 13:56 Wolfram Sang
2014-08-09 17:34 ` Linus Torvalds
     [not found]   ` <CA+55aFy0UVY=60pCr85AvhedfO-MEoD-iMGdWmBYt8fKgF7kWA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-11  1:39     ` Lan Tianyu

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=20141003211053.GA2176@katana \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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).