From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Manish Chopra <manishc@marvell.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
<aelior@marvell.com>, <skalluru@marvell.com>
Subject: Re: [PATCH v2 net 0/2] bnx2x: bug fixes
Date: Sat, 14 Dec 2019 13:04:38 -0800 [thread overview]
Message-ID: <20191214130438.34353698@cakuba.netronome.com> (raw)
In-Reply-To: <20191211175956.11948-1-manishc@marvell.com>
On Wed, 11 Dec 2019 09:59:54 -0800, Manish Chopra wrote:
> This series has two driver changes, one to fix some unexpected
> hardware behaviour casued during the parity error recovery in
> presence of SR-IOV VFs and another one related for fixing resource
> management in the driver among the PFs configured on an engine.
>
> Please consider applying it to "net".
Applied to net, thank you. I'm not queuing for stable because there
were no Fixes tags. Please try to provide those, even if they just
point at the initial driver commit.
prev parent reply other threads:[~2019-12-14 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 17:59 [PATCH v2 net 0/2] bnx2x: bug fixes Manish Chopra
2019-12-11 17:59 ` [PATCH v2 net 1/2] bnx2x: Do not handle requests from VFs after parity Manish Chopra
2019-12-11 17:59 ` [PATCH v2 net 2/2] bnx2x: Fix logic to get total no. of PFs per engine Manish Chopra
2019-12-14 21:04 ` Jakub Kicinski [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=20191214130438.34353698@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=aelior@marvell.com \
--cc=davem@davemloft.net \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=skalluru@marvell.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;
as well as URLs for NNTP newsgroup(s).