On Sun, 14 Mar 2021 14:33:10 +0200 Eran Ben Elisha wrote:
> On 3/11/2021 6:49 PM, Jakub Kicinski wrote:
> > On Thu, 11 Mar 2021 16:23:09 +0200 Eran Ben Elisha wrote:
> >> Would you like Nvidia to reply with the remedy per reporter or to
> >> actually prepare the patch?
> > You mean the patch ad
On 3/11/2021 6:49 PM, Jakub Kicinski wrote:
On Thu, 11 Mar 2021 16:23:09 +0200 Eran Ben Elisha wrote:
On 3/11/2021 5:26 AM, Jakub Kicinski wrote:
Pending vendors adding the right reporters. <<
Would you like Nvidia to reply with the remedy per reporter or to
actually prepare the patch?
You
On Thu, 11 Mar 2021 16:23:09 +0200 Eran Ben Elisha wrote:
> On 3/11/2021 5:26 AM, Jakub Kicinski wrote:
> >>> Pending vendors adding the right reporters. <<
>
> Would you like Nvidia to reply with the remedy per reporter or to
> actually prepare the patch?
You mean the patch adding .remedy? If
On 3/11/2021 5:26 AM, Jakub Kicinski wrote:
Pending vendors adding the right reporters. <<
Would you like Nvidia to reply with the remedy per reporter or to
actually prepare the patch?
Extend the applicability of devlink health reporters
beyond what can be locally remedied. Add failure
>> Pending vendors adding the right reporters. <<
Extend the applicability of devlink health reporters
beyond what can be locally remedied. Add failure modes
which require re-flashing the NVM image or HW changes.
The expectation is that driver will call
devlink_health_reporter_state_update() to p
