From: Wolfram Sang <wsa@kernel.org>
To: netdev@vger.kernel.org
Cc: linux-i2c@vger.kernel.org, Russell King <rmk+kernel@armlinux.org.uk>
Subject: [PULL REQUEST] i2c-fwnode-api-2023017 for netdev
Date: Tue, 17 Jan 2023 09:49:39 +0100 [thread overview]
Message-ID: <Y8ZhI4g0wsvpjokd@ninjato> (raw)
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
Hi,
here is an immtuable branch from I2C requested by Russell King. This
allows him to rework SFP code further.
Please pull.
Wolfram
The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git/ tags/i2c-fwnode-api-2023017
for you to fetch changes up to 373c612d72461ddaea223592df31e62c934aae61:
i2c: add fwnode APIs (2023-01-17 09:29:59 +0100)
----------------------------------------------------------------
Immutable branch adding fwnode API to the I2C core
----------------------------------------------------------------
Russell King (Oracle) (1):
i2c: add fwnode APIs
with much appreciated quality assurance from
----------------------------------------------------------------
Mika Westerberg (1):
(Rev.) i2c: add fwnode APIs
drivers/i2c/i2c-core-acpi.c | 13 +-----
drivers/i2c/i2c-core-base.c | 98 +++++++++++++++++++++++++++++++++++++++++++++
drivers/i2c/i2c-core-of.c | 66 ------------------------------
include/linux/i2c.h | 24 +++++++++--
4 files changed, 120 insertions(+), 81 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-01-17 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 8:49 Wolfram Sang [this message]
2023-01-18 3:30 ` [PULL REQUEST] i2c-fwnode-api-2023017 for netdev patchwork-bot+netdevbpf
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=Y8ZhI4g0wsvpjokd@ninjato \
--to=wsa@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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