netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yuval Mintz <Yuval.Mintz@cavium.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: Yuval Mintz <Yuval.Mintz@cavium.com>
Subject: [PATCH net-next 0/7] qed*: Patch series
Date: Sun, 30 Oct 2016 18:38:30 +0200	[thread overview]
Message-ID: <1477845517-17228-1-git-send-email-Yuval.Mintz@cavium.com> (raw)

This series does several things. The bigger changes:

 - Add new notification APIs [& Defaults] for various fields.
The series then utilizes some of those qed <-> qede APIs to bass WoL
support upon.

 - Change the resource allocation scheme to receive the values from
management firmware, instead of equally sharing resources between
functions [that might not need those]. That would, e.g., allow us to
configure additional filters to network interfaces in presence of
storage [PCI] functions from same adapter.

Dave,

Please consider applying this series to `net-next'.

Thanks,
Yuval

Sudarsana Kalluru (1):
  qed*: Management firmware - notifications and defaults

Tomer Tayar (1):
  qed: Learn resources from management firmware

Yuval Mintz (5):
  qed: Add nvram selftest
  qed*: Add support for WoL
  qede: Decouple ethtool caps from qed
  qed: Learn of RDMA capabilities per-device
  qed: Use VF-queue feature

 drivers/net/ethernet/qlogic/qed/qed.h           |  19 +-
 drivers/net/ethernet/qlogic/qed/qed_dev.c       | 382 +++++++++++++++++----
 drivers/net/ethernet/qlogic/qed/qed_hsi.h       | 120 ++++++-
 drivers/net/ethernet/qlogic/qed/qed_int.c       |  32 +-
 drivers/net/ethernet/qlogic/qed/qed_l2.c        |   2 +-
 drivers/net/ethernet/qlogic/qed/qed_main.c      | 105 ++++++
 drivers/net/ethernet/qlogic/qed/qed_mcp.c       | 433 +++++++++++++++++++++++-
 drivers/net/ethernet/qlogic/qed/qed_mcp.h       | 158 +++++++++
 drivers/net/ethernet/qlogic/qed/qed_selftest.c  | 101 ++++++
 drivers/net/ethernet/qlogic/qed/qed_selftest.h  |  10 +
 drivers/net/ethernet/qlogic/qed/qed_sriov.c     |  17 +-
 drivers/net/ethernet/qlogic/qede/qede.h         |   2 +
 drivers/net/ethernet/qlogic/qede/qede_ethtool.c |  54 ++-
 drivers/net/ethernet/qlogic/qede/qede_main.c    |  17 +
 include/linux/qed/qed_eth_if.h                  |   2 +-
 include/linux/qed/qed_if.h                      |  47 +++
 16 files changed, 1404 insertions(+), 97 deletions(-)

-- 
1.9.3

             reply	other threads:[~2016-10-30 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30 16:38 Yuval Mintz [this message]
2016-10-30 16:38 ` [PATCH net-next 1/7] qed*: Management firmware - notifications and defaults Yuval Mintz
2016-10-30 16:38 ` [PATCH net-next 2/7] qed: Add nvram selftest Yuval Mintz
2016-10-30 16:38 ` [PATCH net-next 3/7] qed*: Add support for WoL Yuval Mintz
2016-10-30 16:38 ` [PATCH net-next 4/7] qede: Decouple ethtool caps from qed Yuval Mintz
2016-10-30 16:38 ` [PATCH net-next 5/7] qed: Learn of RDMA capabilities per-device Yuval Mintz
2016-10-30 16:38 ` [PATCH net-next 6/7] qed: Use VF-queue feature Yuval Mintz
2016-10-30 16:38 ` [PATCH net-next 7/7] qed: Learn resources from management firmware Yuval Mintz
2016-10-30 21:26 ` [PATCH net-next 0/7] qed*: Patch series David Miller

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=1477845517-17228-1-git-send-email-Yuval.Mintz@cavium.com \
    --to=yuval.mintz@cavium.com \
    --cc=davem@davemloft.net \
    --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).