linux-kernel.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.12
Date: Fri, 23 Jun 2017 20:27:10 +0200	[thread overview]
Message-ID: <20170623182706.mkz65j55re4koakc@ninjato> (raw)

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

Linus,

I2C has another driver bugfix for you. Please pull.

Thanks,

   Wolfram


The following changes since commit 41f1830f5a7af77cf5c86359aba3cbd706687e52:

  Linux 4.12-rc6 (2017-06-19 22:19:37 +0800)

are available in the git repository at:

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

for you to fetch changes up to 6c782a5ea56a799658e213a78dc1455264938afa:

  i2c: imx: Use correct function to write to register (2017-06-22 10:52:02 +0200)

----------------------------------------------------------------
Michail Georgios Etairidis (1):
      i2c: imx: Use correct function to write to register

 drivers/i2c/busses/i2c-imx.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

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

             reply	other threads:[~2017-06-23 18:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 18:27 Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-06-18 12:58 [PULL REQUEST] i2c for 4.12 Wolfram Sang
2017-05-23  7:30 Wolfram Sang
2017-05-19 20:40 Wolfram Sang
2017-05-22 20:11 ` Linus Torvalds
2017-05-22 20:14   ` Wolfram Sang
2017-05-22 20:28     ` Linus Torvalds
2017-05-22 20:32       ` Linus Torvalds
2017-05-22 21:04         ` Wolfram Sang
2017-05-22 21:37           ` Tobias Klausmann
2017-05-17  7:27 Wolfram Sang
2017-05-03 14:41 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=20170623182706.mkz65j55re4koakc@ninjato \
    --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).