From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Bornyakov <i.bornyakov@metrotek.ru>
Cc: netdev@vger.kernel.org, linux@armlinux.org.uk, andrew@lunn.ch,
hkallweit1@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
system@metrotek.ru
Subject: Re: [PATCH net v2 0/2] fix EEPROM read of absent SFP module
Date: Sun, 09 Apr 2023 15:10:18 +0000 [thread overview]
Message-ID: <168105301836.30484.7699646579185070027.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230406130833.32160-1-i.bornyakov@metrotek.ru>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 6 Apr 2023 16:08:31 +0300 you wrote:
> The patchset is to improve EEPROM read requests when SFP module is
> absent.
>
> ChangeLog:
> v1:
> https://lore.kernel.org/netdev/20230405153900.747-1-i.bornyakov@metrotek.ru/
> v2:
> * reword commit message of "net: sfp: initialize sfp->i2c_block_size
> at sfp allocation"
> * add second patch to eliminate excessive I2C transfers in
> sfp_module_eeprom() and sfp_module_eeprom_by_page()
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: sfp: initialize sfp->i2c_block_size at sfp allocation
https://git.kernel.org/netdev/net/c/813c2dd78618
- [net,v2,2/2] net: sfp: avoid EEPROM read of absent SFP module
https://git.kernel.org/netdev/net/c/bef227c1537c
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:[~2023-04-09 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 13:08 [PATCH net v2 0/2] fix EEPROM read of absent SFP module Ivan Bornyakov
2023-04-06 13:08 ` [PATCH net v2 1/2] net: sfp: initialize sfp->i2c_block_size at sfp allocation Ivan Bornyakov
2023-04-06 14:05 ` Andrew Lunn
2023-04-06 13:08 ` [PATCH net v2 2/2] net: sfp: avoid EEPROM read of absent SFP module Ivan Bornyakov
2023-04-06 14:06 ` Andrew Lunn
2023-04-09 15:10 ` 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=168105301836.30484.7699646579185070027.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=i.bornyakov@metrotek.ru \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=system@metrotek.ru \
/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