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.14-rc1-take2
Date: Thu, 30 Jan 2025 22:38:57 +0100 [thread overview]
Message-ID: <Z5vxcfD8RPYzfsCe@shikoro> (raw)
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
The following changes since commit d0d106a2bd21499901299160744e5fe9f4c83ddb:
Merge tag 'bpf-next-6.14' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next (2025-01-23 08:04:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git tags/i2c-for-6.14-rc1-take2
for you to fetch changes up to 6250ebe666e425e173df5e11e8a612d57921f48d:
i2c: Fix core-managed per-client debugfs handling (2025-01-26 12:03:54 +0100)
----------------------------------------------------------------
i2c-for-6.14-rc1-take2
Fixes two issues introduced with the first pull request:
- add a missing Kconfig dependency for imx-lpi2c
- in the core, handle the new per-client debugfs directory during
probe/remove, not during {un}register
----------------------------------------------------------------
Arnd Bergmann (1):
i2c: imx-lpi2c: select CONFIG_I2C_SLAVE
Guenter Roeck (1):
i2c: Fix core-managed per-client debugfs handling
drivers/i2c/busses/Kconfig | 1 +
drivers/i2c/i2c-core-base.c | 9 ++++++---
2 files changed, 7 insertions(+), 3 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-01-30 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 21:38 Wolfram Sang [this message]
2025-01-31 2:00 ` [PULL REQUEST] i2c-for-6.14-rc1-take2 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=Z5vxcfD8RPYzfsCe@shikoro \
--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