From: David Miller <davem@davemloft.net>
To: vikas.gupta@broadcom.com
Cc: michael.chan@broadcom.com, jiri@mellanox.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
vasundhara-v.volam@broadcom.com, vikram.prakash@broadcom.com
Subject: Re: [PATCH INTERNAL v1 0/3] Devlink notification after recovery complete by bnxt_en driver
Date: Wed, 08 Jan 2020 15:48:05 -0800 (PST) [thread overview]
Message-ID: <20200108.154805.1094700915467259339.davem@davemloft.net> (raw)
In-Reply-To: <1577980091-25118-1-git-send-email-vikas.gupta@broadcom.com>
From: Vikas Gupta <vikas.gupta@broadcom.com>
Date: Thu, 2 Jan 2020 21:18:08 +0530
> This patchset adds following feature in devlink
> 1) Recovery complete direct call API to be used by drivers when it
> successfully completes. It is required as recovery triggered by
> devlink may return with EINPROGRESS and eventually recovery
> completes in different context.
> 2) A notification when health status is updated by reporter.
>
> Patchset also contains required changes in bnxt_en driver to
> mark recovery in progress when recovery is triggered from kernel
> devlink.
Series applied to net-next, thanks.
prev parent reply other threads:[~2020-01-08 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 15:48 Vikas Gupta
2020-01-02 15:48 ` [PATCH v1 1/3] devlink: add support for reporter recovery completion Vikas Gupta
2020-01-02 15:48 ` [PATCH v1 2/3] devlink: add devink notification when reporter update health state Vikas Gupta
2020-01-02 15:48 ` [PATCH v1 3/3] bnxt_en: Call recovery done after reset is successfully done Vikas Gupta
2020-01-05 22:07 ` [PATCH INTERNAL v1 0/3] Devlink notification after recovery complete by bnxt_en driver David Miller
2020-01-08 23:48 ` David Miller [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=20200108.154805.1094700915467259339.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vasundhara-v.volam@broadcom.com \
--cc=vikas.gupta@broadcom.com \
--cc=vikram.prakash@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
all inboxes | Powered by JetHome®