From: Jiri Pirko <jiri@resnulli.us>
To: Edwin Peer <edwin.peer@broadcom.com>
Cc: Vasundhara Volam <vasundhara-v.volam@broadcom.com>,
David Miller <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/4] bnxt_en: Add new "enable_hot_fw_reset" generic devlink parameter
Date: Tue, 19 May 2020 09:29:23 +0200 [thread overview]
Message-ID: <20200519072923.GD4655@nanopsycho> (raw)
In-Reply-To: <CAKOOJTxVbJ0QUCUz8JKDSJKoiQ8FecifbRRo9gcM8ijhDkA9HA@mail.gmail.com>
Tue, May 19, 2020 at 09:13:46AM CEST, edwin.peer@broadcom.com wrote:
>On Mon, May 18, 2020 at 10:27 PM Jiri Pirko <jiri@resnulli.us> wrote:
>
>> >I am adding this param to control the fw hot reset capability of the device.
>>
>> I don't follow, sorry. Could you be more verbose about what you are
>> trying to achieve here?
>
>Hi Jiri,
>
>Vasundhara is not adding a mechanism to trigger the actual reset here.
>This is a parameter to enable or disable the hot reset functionality.
>It's configuration, not an action.
I understand is it not an action.
But I think I missed what exactly it configures. I still don't have a
clue.
>
>Regards,
>Edwin Peer
prev parent reply other threads:[~2020-05-19 7:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 8:27 [PATCH net-next 0/4] bnxt_en: Add new "enable_hot_fw_reset" generic devlink parameter Vasundhara Volam
2020-05-18 8:27 ` [PATCH net-next 1/4] devlink: Add new "enable_hot_fw_reset" generic device parameter Vasundhara Volam
2020-05-18 8:27 ` [PATCH net-next 2/4] bnxt_en: Update firmware spec. to 1.10.1.40 Vasundhara Volam
2020-05-18 8:27 ` [PATCH net-next 3/4] bnxt_en: Use enable_hot_fw_reset generic devlink parameter Vasundhara Volam
2020-05-18 8:27 ` [PATCH net-next 4/4] bnxt_en: Check if hot_fw_reset is allowed before doing ETHTOOL_RESET Vasundhara Volam
2020-05-18 11:01 ` [PATCH net-next 0/4] bnxt_en: Add new "enable_hot_fw_reset" generic devlink parameter Jiri Pirko
2020-05-18 23:43 ` Jakub Kicinski
2020-05-19 5:24 ` Jiri Pirko
2020-05-19 17:44 ` Jakub Kicinski
2020-05-19 4:31 ` Vasundhara Volam
2020-05-19 5:27 ` Jiri Pirko
2020-05-19 5:43 ` Vasundhara Volam
2020-05-19 7:30 ` Jiri Pirko
2020-05-19 8:41 ` Michael Chan
2020-05-19 9:41 ` Jiri Pirko
2020-05-19 10:50 ` Vasundhara Volam
2020-05-19 13:25 ` Jiri Pirko
2020-05-19 7:13 ` Edwin Peer
2020-05-19 7:29 ` Jiri Pirko [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=20200519072923.GD4655@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edwin.peer@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vasundhara-v.volam@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 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.