linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	Peter Rosin <peda@axentia.se>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PULL REQUEST] i2c for 5.12
Date: Sat, 17 Apr 2021 19:18:16 +0200	[thread overview]
Message-ID: <20210417171816.GA2369@kunai> (raw)

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

Linus,

here is one more driver bugfix for I2C.

Please pull.

Thanks,

   Wolfram


The following changes since commit d434405aaab7d0ebc516b68a8fc4100922d7f5ef:

  Linux 5.12-rc7 (2021-04-11 15:16:13 -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 39930213e7779b9c4257499972b8afb8858f1a2d:

  i2c: mv64xxx: Fix random system lock caused by runtime PM (2021-04-15 22:13:19 +0200)

----------------------------------------------------------------
Marek Behún (1):
      i2c: mv64xxx: Fix random system lock caused by runtime PM


with much appreciated quality assurance from
----------------------------------------------------------------
Samuel Holland (1):
      (Rev.) i2c: mv64xxx: Fix random system lock caused by runtime PM

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

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

             reply	other threads:[~2021-04-17 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17 17:18 Wolfram Sang [this message]
2021-04-17 19:08 ` [PULL REQUEST] i2c for 5.12 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2021-04-10 11:00 Wolfram Sang
2021-04-10 17:03 ` pr-tracker-bot

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=20210417171816.GA2369@kunai \
    --to=wsa@kernel.org \
    --cc=brgl@bgdev.pl \
    --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;
as well as URLs for NNTP newsgroup(s).