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>,
Andi Shyti <andi.shyti@kernel.org>
Subject: [PULL REQUEST] i2c-for-6.4-rc8
Date: Sun, 25 Jun 2023 13:23:03 +0200 [thread overview]
Message-ID: <ZJgjl6fXM50EofPk@sai> (raw)
[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]
The following changes since commit 45a3e24f65e90a047bef86f927ebdc4c710edaa1:
Linux 6.4-rc7 (2023-06-18 14:06:27 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git tags/i2c-for-6.4-rc8
for you to fetch changes up to e69b9bc170c6d93ee375a5cbfd15f74c0fb59bdd:
i2c: imx-lpi2c: fix type char overflow issue when calculating the clock cycle (2023-06-23 12:58:24 +0200)
----------------------------------------------------------------
Nothing fancy. Two driver and one DT binding fix.
----------------------------------------------------------------
Clark Wang (1):
i2c: imx-lpi2c: fix type char overflow issue when calculating the clock cycle
Rob Herring (1):
dt-bindings: i2c: opencores: Add missing type for "regstep"
Shuai Jiang (1):
i2c: qup: Add missing unwind goto in qup_i2c_probe()
with much appreciated quality assurance from
----------------------------------------------------------------
Andi Shyti (2):
(Rev.) i2c: imx-lpi2c: fix type char overflow issue when calculating the clock cycle
(Rev.) i2c: qup: Add missing unwind goto in qup_i2c_probe()
Andrew Lunn (1):
(Rev.) dt-bindings: i2c: opencores: Add missing type for "regstep"
Conor Dooley (1):
(Rev.) dt-bindings: i2c: opencores: Add missing type for "regstep"
Dongliang Mu (1):
(Rev.) i2c: qup: Add missing unwind goto in qup_i2c_probe()
Peter Korsgaard (1):
(Rev.) dt-bindings: i2c: opencores: Add missing type for "regstep"
.../bindings/i2c/opencores,i2c-ocores.yaml | 1 +
drivers/i2c/busses/i2c-imx-lpi2c.c | 4 ++--
drivers/i2c/busses/i2c-qup.c | 21 ++++++++++++++-------
3 files changed, 17 insertions(+), 9 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-06-25 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 11:23 Wolfram Sang [this message]
2023-06-25 23:31 ` [PULL REQUEST] i2c-for-6.4-rc8 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=ZJgjl6fXM50EofPk@sai \
--to=wsa@kernel.org \
--cc=andi.shyti@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