From: patchwork-bot+netdevbpf@kernel.org
To: Jonas Jelonek <jelonek.jonas@gmail.com>
Cc: linux@armlinux.org.uk, andrew@lunn.ch, hkallweit1@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, maxime.chevallier@bootlin.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bjorn@mork.no, horms@kernel.org
Subject: Re: [PATCH net-next v11 0/2] net: sfp: extend SMBus support
Date: Mon, 15 Jun 2026 21:20:37 +0000 [thread overview]
Message-ID: <178155843738.301119.9459899533729939488.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260614133418.2068201-1-jelonek.jonas@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 14 Jun 2026 13:34:16 +0000 you wrote:
> Today, the SFP driver only drives I2C adapters that advertise full
> I2C_FUNC_I2C, or SMBus-only adapters via single-byte transfers (with
> hwmon disabled). Several SoCs ship I2C/SMBus-only controllers that
> support more than just byte access -- e.g. word and I2C block -- and
> have SFP cages wired to them. Today, those adapters either work
> poorly or not at all.
>
> [...]
Here is the summary with links:
- [net-next,v11,1/2] net: sfp: apply I2C adapter quirks to limit block size
https://git.kernel.org/netdev/net-next/c/f2a138abfb71
- [net-next,v11,2/2] net: sfp: extend SMBus support
https://git.kernel.org/netdev/net-next/c/58b29bdf6186
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-15 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 13:34 [PATCH net-next v11 0/2] net: sfp: extend SMBus support Jonas Jelonek
2026-06-14 13:34 ` [PATCH net-next v11 1/2] net: sfp: apply I2C adapter quirks to limit block size Jonas Jelonek
2026-06-14 13:34 ` [PATCH net-next v11 2/2] net: sfp: extend SMBus support Jonas Jelonek
2026-06-14 17:17 ` Maxime Chevallier
2026-06-15 21:20 ` patchwork-bot+netdevbpf [this message]
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=178155843738.301119.9459899533729939488.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=jelonek.jonas@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.