From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@cavium.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/7] qed*: Patch series
Date: Mon, 31 Oct 2016 15:52:54 -0400 (EDT) [thread overview]
Message-ID: <20161031.155254.2213369781807264171.davem@davemloft.net> (raw)
In-Reply-To: <1477890867-3789-1-git-send-email-Yuval.Mintz@cavium.com>
From: Yuval Mintz <Yuval.Mintz@cavium.com>
Date: Mon, 31 Oct 2016 07:14:20 +0200
> 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.
Series applied, thanks.
prev parent reply other threads:[~2016-10-31 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 5:14 [PATCH net-next v2 0/7] qed*: Patch series Yuval Mintz
2016-10-31 5:14 ` [PATCH net-next v2 1/7] qed*: Management firmware - notifications and defaults Yuval Mintz
2016-10-31 5:14 ` [PATCH net-next v2 2/7] qed: Add nvram selftest Yuval Mintz
2016-10-31 5:14 ` [PATCH net-next v2 3/7] qed*: Add support for WoL Yuval Mintz
2016-10-31 5:14 ` [PATCH net-next v2 4/7] qede: Decouple ethtool caps from qed Yuval Mintz
2016-10-31 5:14 ` [PATCH net-next v2 5/7] qed: Learn of RDMA capabilities per-device Yuval Mintz
2016-10-31 5:14 ` [PATCH net-next v2 6/7] qed: Use VF-queue feature Yuval Mintz
2016-10-31 5:14 ` [PATCH net-next v2 7/7] qed: Learn resources from management firmware Yuval Mintz
2016-10-31 19:52 ` 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=20161031.155254.2213369781807264171.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Yuval.Mintz@cavium.com \
--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).