netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@qlogic.com
Cc: netdev@vger.kernel.org, James.bottomley@HansenPartnership.com,
	linux-scsi-owner@vger.kernel.org, chad.dupuis@qlogic.com,
	Ariel.Elior@qlogic.com
Subject: Re: [PATCH v2 net-next 0/4] bnx2x, cnic, bnx2fc: add support for BD
Date: Thu, 06 Aug 2015 21:54:29 -0700 (PDT)	[thread overview]
Message-ID: <20150806.215429.1576532174279680769.davem@davemloft.net> (raw)
In-Reply-To: <1438670250-20130-1-git-send-email-Yuval.Mintz@qlogic.com>

From: Yuval Mintz <Yuval.Mintz@qlogic.com>
Date: Tue, 4 Aug 2015 09:37:26 +0300

> Commit 230d00eb4bfe ("bnx2x: new Multi-function mode - BD") added support
> for a new multi-function mode, but it added only the support required by
> bnx2x for L2 interfaces.
> 
> This adds the required changes to support the new multi-function mode in
> the offloaded storage protocols.
> 
> Dave,
> 
> Please consider applying this series to `net-next'.
> 
> Do notice that this involves non-networking driver changes -
> but sending this as a single series seemed like the best approach as
> we had to have bnx2x changes to support the new functionality.
> If this is problematic, please tell us what's the preferred solution here.

Series applied, thanks.

      parent reply	other threads:[~2015-08-07  4:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04  6:37 [PATCH v2 net-next 0/4] bnx2x, cnic, bnx2fc: add support for BD Yuval Mintz
2015-08-04  6:37 ` [PATCH v2 net-next 1/4] cnic: Populate upper layer driver state in MFW Yuval Mintz
2015-08-04  6:37 ` [PATCH v2 net-next 2/4] cnic: Add the interfaces to get FC-NPIV table Yuval Mintz
2015-08-04  6:37 ` [PATCH v2 net-next 3/4] bnx2x: Add BD support for storage Yuval Mintz
2015-08-04  6:37 ` [PATCH v2 net-next 4/4] bnx2fc: Read npiv table from nvram and create vports Yuval Mintz
2015-08-07  4:54 ` 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=20150806.215429.1576532174279680769.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Ariel.Elior@qlogic.com \
    --cc=James.bottomley@HansenPartnership.com \
    --cc=Yuval.Mintz@qlogic.com \
    --cc=chad.dupuis@qlogic.com \
    --cc=linux-scsi-owner@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).