From: Jakub Kicinski <kuba@kernel•org>
To: linux@armlinux•org.uk
Cc: Ivan Bornyakov <i.bornyakov@metrotek•ru>,
netdev@vger•kernel.org, andrew@lunn•ch, hkallweit1@gmail•com,
davem@davemloft•net, edumazet@google•com, pabeni@redhat•com,
linux-kernel@vger•kernel.org, system@metrotek•ru,
stable@vger•kernel.org
Subject: Re: [PATCH net] net: sfp: initialize sfp->i2c_block_size at sfp allocation
Date: Thu, 6 Apr 2023 19:02:08 -0700 [thread overview]
Message-ID: <20230406190208.7918c71e@kernel.org> (raw)
In-Reply-To: <20230405153900.747-1-i.bornyakov@metrotek.ru>
On Wed, 5 Apr 2023 18:39:00 +0300 Ivan Bornyakov wrote:
> sfp->i2c_block_size is initialized at SFP module insertion in
> sfp_sm_mod_probe(). Because of that, if SFP module was not inserted
> since boot, ethtool -m leads to zero-length I2C read attempt.
>
> # ethtool -m xge0
> i2c i2c-3: adapter quirk: no zero length (addr 0x0050, size 0, read)
> Cannot get Module EEPROM data: Operation not supported
>
> If SFP module was plugged then removed at least once,
> sfp->i2c_block_size will be initialized and ethtool -m will fail with
> different error
>
> # ethtool -m xge0
> Cannot get Module EEPROM data: Remote I/O error
>
> Fix this by initializing sfp->i2_block_size at struct sfp allocation
> stage so ethtool -m with SFP module removed will fail the same way, i.e.
> -EREMOTEIO, in both cases and without errors from I2C adapter.
Hi Russell - yes / no / come back when both patches are ready?
prev parent reply other threads:[~2023-04-07 2:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 15:39 [PATCH net] net: sfp: initialize sfp->i2c_block_size at sfp allocation Ivan Bornyakov
2023-04-05 19:35 ` Andrew Lunn
2023-04-05 20:41 ` Ivan Bornyakov
2023-04-05 20:51 ` Andrew Lunn
2023-04-05 21:13 ` Ivan Bornyakov
2023-04-07 2:02 ` Jakub Kicinski [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=20230406190208.7918c71e@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hkallweit1@gmail$(echo .)com \
--cc=i.bornyakov@metrotek$(echo .)ru \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=stable@vger$(echo .)kernel.org \
--cc=system@metrotek$(echo .)ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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