From: Bert Kenward <bkenward@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>,
Solarflare linux maintainers <linux-net-drivers@solarflare.com>
Subject: [PATCH net-next v2 0/5] sfc: additional virtual function support
Date: Wed, 23 Dec 2015 08:55:12 +0000 [thread overview]
Message-ID: <567A6170.6010104@solarflare.com> (raw)
In-Reply-To: <5674274C.4020606@solarflare.com>
This introduces the client side of a mechanism to defer authorisation of
operations, for example multicast subscription. Although primarily aimed at
SRIOV VFs this can also apply to unprivileged PFs.
Also handle reboot ordering corner cases better and reduce the level of some
logging.
v2: remove #ifdef DEBUG around new WARN_ON in mcdi.c.
Bert Kenward (4):
sfc: Retry MCDI after NO_EVB_PORT error on a VF
sfc: Handle MCDI proxy authorisation
sfc: Make failed filter removal less noisy
sfc: Downgrade or remove some error messages
Tomáš Pilař (1):
sfc: Downgrade EPERM messages from MCDI to debug
drivers/net/ethernet/sfc/ef10.c | 68 +++++++----
drivers/net/ethernet/sfc/efx.c | 7 +-
drivers/net/ethernet/sfc/mcdi.c | 250 ++++++++++++++++++++++++++++++++++++----
drivers/net/ethernet/sfc/mcdi.h | 10 ++
4 files changed, 288 insertions(+), 47 deletions(-)
--
2.4.3
next parent reply other threads:[~2015-12-23 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5674274C.4020606@solarflare.com>
2015-12-23 8:55 ` Bert Kenward [this message]
2015-12-23 8:56 ` [PATCH net-next v2 1/5] sfc: Retry MCDI after NO_EVB_PORT error on a VF Bert Kenward
2015-12-23 8:57 ` [PATCH net-next v2 2/5] sfc: Handle MCDI proxy authorisation Bert Kenward
2015-12-23 8:57 ` [PATCH net-next v2 3/5] sfc: Make failed filter removal less noisy Bert Kenward
2015-12-23 8:57 ` [PATCH net-next v2 4/5] sfc: Downgrade EPERM messages from MCDI to debug Bert Kenward
2015-12-23 8:58 ` [PATCH net-next v2 5/5] sfc: Downgrade or remove some error messages Bert Kenward
2015-12-24 3:06 ` [PATCH net-next v2 0/5] sfc: additional virtual function support 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=567A6170.6010104@solarflare.com \
--to=bkenward@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-net-drivers@solarflare.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).