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] for-6.7-rc1-part2
Date: Thu, 9 Nov 2023 07:59:25 +0100 [thread overview]
Message-ID: <ZUyDTXUSNgMQFNAh@ninjato> (raw)
[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]
The following changes since commit 305230142ae0637213bf6e04f6d9f10bbcb74af8:
Merge tag 'pm-6.7-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm (2023-11-07 17:16:23 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git tags/for-6.7-rc1-part2
for you to fetch changes up to bdba49cbba41f0bea54fc93529bbef4d6ceaa3cd:
i2c: cp2615: Fix 'assignment to __be16' warning (2023-11-08 10:27:17 +0100)
----------------------------------------------------------------
The second I2C pull request for 6.7-rc1 contains one patch which slipped
through the cracks (iproc), a core sanitizing improvement as the new
memdup_array_user() helper went upstream (i2c-dev), and two driver
bugfixes (designware, cp2615).
----------------------------------------------------------------
Bence Csókás (1):
i2c: cp2615: Fix 'assignment to __be16' warning
Philipp Stanner (1):
i2c: dev: copy userspace array safely
Roman Bacik (1):
i2c: iproc: handle invalid slave state
Tam Nguyen (1):
i2c: designware: Disable TX_EMPTY irq while waiting for block length byte
with much appreciated quality assurance from
----------------------------------------------------------------
Serge Semin (1):
(Rev.) i2c: designware: Disable TX_EMPTY irq while waiting for block length byte
drivers/i2c/busses/i2c-bcm-iproc.c | 133 ++++++++++++++++-------------
drivers/i2c/busses/i2c-cp2615.c | 2 +-
drivers/i2c/busses/i2c-designware-master.c | 19 ++++-
drivers/i2c/i2c-dev.c | 4 +-
4 files changed, 94 insertions(+), 64 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-11-09 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 6:59 Wolfram Sang [this message]
2023-11-09 22:28 ` [PULL REQUEST] for-6.7-rc1-part2 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=ZUyDTXUSNgMQFNAh@ninjato \
--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