From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@cavium.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/9] qed: IOV related clenaups
Date: Tue, 21 Mar 2017 19:02:51 -0700 (PDT) [thread overview]
Message-ID: <20170321.190251.1441053484481490457.davem@davemloft.net> (raw)
In-Reply-To: <1489921700-6850-1-git-send-email-Yuval.Mintz@cavium.com>
From: Yuval Mintz <Yuval.Mintz@cavium.com>
Date: Sun, 19 Mar 2017 13:08:11 +0200
> This patch series targets IOV functionality [on both PF and VF].
>
> Patches #2, #3 and #5 fix flows relating to malicious VFs, either by
> upgrading and aligning current safe-guards or by correcing racy flows.
>
> Patches #1 and #8 make some malicious/dysnfunctional VFs logging appear
> by default in logs.
>
> The rest of the patches either cleanup the existing code or else correct
> some possible [yet fairly insignicant] issues in VF behavior.
Series applied, thank you.
prev parent reply other threads:[~2017-03-22 2:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 11:08 [PATCH net-next 0/9] qed: IOV related clenaups Yuval Mintz
2017-03-19 11:08 ` [PATCH net-next 1/9] qed: Increase verbosity of VF -> PF errors Yuval Mintz
2017-03-19 11:08 ` [PATCH net-next 2/9] qed: Clean VF malicious indication when disabling IOV Yuval Mintz
2017-03-19 11:08 ` [PATCH net-next 3/9] qed: Set HW-channel to ready before ACKing VF Yuval Mintz
2017-03-19 11:08 ` [PATCH net-next 4/9] qed: Correct default VF coalescing configuration Yuval Mintz
2017-03-19 11:08 ` [PATCH net-next 5/9] qed: Uniform IOV queue validation Yuval Mintz
2017-03-19 11:08 ` [PATCH net-next 6/9] qed: Deprecate VF multiple queue-stop Yuval Mintz
2017-03-19 11:08 ` [PATCH net-next 7/9] qed: Make qed_iov_mark_vf_flr() return bool Yuval Mintz
2017-03-19 11:08 ` [PATCH net-next 8/9] qed: Raise verbosity of Malicious VF indications Yuval Mintz
2017-03-19 11:08 ` [PATCH net-next 9/9] qed: Always publish VF link from leading hwfn Yuval Mintz
2017-03-22 2:02 ` 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=20170321.190251.1441053484481490457.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).