Sat, Sep 07, 2019 at 06:17:30AM CEST, jakub.kicin...@netronome.com wrote:
>On Fri, 6 Sep 2019 11:40:54 -0700, Dirk van der Merwe wrote:
>> >> DEVLINK_PARAM_RESET_DEV_VALUE_UNKNOWN (0)
>> >> + Unknown or invalid value.
>> > Why do you need this? Do you have usecase for this value
On Fri, 6 Sep 2019 11:40:54 -0700, Dirk van der Merwe wrote:
> >> DEVLINK_PARAM_RESET_DEV_VALUE_UNKNOWN (0)
> >> +Unknown or invalid value.
> > Why do you need this? Do you have usecase for this value?
>
> I added this in to avoid having the entire netlink dump fail when th
On 9/6/19 11:31 AM, Jiri Pirko wrote:
Fri, Sep 06, 2019 at 06:00:52PM CEST, simon.hor...@netronome.com wrote:
From: Dirk van der Merwe
Add the 'reset_dev_on_drv_probe' devlink parameter, controlling the
device reset policy on driver probe.
This parameter is useful in conjunction with the ex
Fri, Sep 06, 2019 at 06:00:52PM CEST, simon.hor...@netronome.com wrote:
>From: Dirk van der Merwe
>
>Add the 'reset_dev_on_drv_probe' devlink parameter, controlling the
>device reset policy on driver probe.
>
>This parameter is useful in conjunction with the existing
>'fw_load_policy' parameter.
>
From: Dirk van der Merwe
Add the 'reset_dev_on_drv_probe' devlink parameter, controlling the
device reset policy on driver probe.
This parameter is useful in conjunction with the existing
'fw_load_policy' parameter.
Signed-off-by: Dirk van der Merwe
Signed-off-by: Simon Horman
---
Documentat
