From: Ido Schimmel <idosch@idosch.org>
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, gospo@broadcom.com,
vikas.gupta@broadcom.com
Subject: Re: [PATCH net-next v3 2/3] bnxt_en: add .get_module_eeprom_by_page() support
Date: Sat, 22 Oct 2022 16:53:25 +0300 [thread overview]
Message-ID: <Y1P11byyH1oEuZqi@shredder> (raw)
In-Reply-To: <1666334243-23866-3-git-send-email-michael.chan@broadcom.com>
On Fri, Oct 21, 2022 at 02:37:22AM -0400, Michael Chan wrote:
> From: Vikas Gupta <vikas.gupta@broadcom.com>
>
> Add support for .get_module_eeprom_by_page() callback which
> implements generic solution for module`s eeprom access.
>
> v3: Add bnxt_get_module_status() to get a more specific extack error
> string.
> Return -EINVAL from bnxt_get_module_eeprom_by_page() when we
> don't want to fallback to old method.
> v2: Simplification suggested by Ido Schimmel
>
> Link: https://lore.kernel.org/netdev/YzVJ%2FvKJugoz15yV@shredder/
> Cc: Ido Schimmel <idosch@idosch.org>
> Signed-off-by: Vikas Gupta <vikas.gupta@broadcom.com>
> Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
next prev parent reply other threads:[~2022-10-22 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 6:37 [PATCH net-next v3 0/3] bnxt_en: Driver updates Michael Chan
2022-10-21 6:37 ` [PATCH net-next v3 1/3] bnxt_en: Update firmware interface to 1.10.2.118 Michael Chan
2022-10-21 6:37 ` [PATCH net-next v3 2/3] bnxt_en: add .get_module_eeprom_by_page() support Michael Chan
2022-10-22 13:53 ` Ido Schimmel [this message]
2022-10-21 6:37 ` [PATCH net-next v3 3/3] bnxt_en: check and resize NVRAM UPDATE entry before flashing Michael Chan
2022-10-25 3:30 ` [PATCH net-next v3 0/3] bnxt_en: Driver updates 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=Y1P11byyH1oEuZqi@shredder \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gospo@broadcom.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vikas.gupta@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox