From: Sathya Perla <sathya.perla@emulex.com>
To: <netdev@vger.kernel.org>
Subject: [PATCH 0/3] be2net: patch set
Date: Fri, 20 Mar 2015 06:28:22 -0400 [thread overview]
Message-ID: <1426847305-23008-1-git-send-email-sathya.perla@emulex.com> (raw)
Hi David, this patch set includes 3 bug fixes to the be2net driver.
Patch 1 fixes a vlan isolation issue with VFs. When a VF is placed in
promiscous mode, it could receive packets belonging to any vlan, as
the PF driver grants vlan promisc capability to VFs. The PF
driver now disables the vlan promisc capability for VFs to fix this
problem.
Patch 2 fixes the call to MODIFY_EQ_DELAY FW cmd to not include more
than 8 EQs per cmd. The FW is not capable of handling more than 8 EQs
per cmd.
Patch 3 fixes an EEH error detection issue. On Power platforms,
when an EEH error occurs, the slot disconnect state is more reliably
detected via an MMIO read compared to a config read. So, the error
register reads that occur every second are now done via MMIO.
Pls apply this patch set to the "net" tree. Thanks!
Suresh Reddy (2):
be2net: restrict MODIFY_EQ_DELAY cmd to a max of 8 EQs
be2net: use PCI MMIO read instead of config read for errors
Vasundhara Volam (1):
be2net: Prevent VFs from enabling VLAN promiscuous mode
next reply other threads:[~2015-03-20 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 10:28 Sathya Perla [this message]
2015-03-20 10:28 ` [PATCH 1/3] be2net: Prevent VFs from enabling VLAN promiscuous mode Sathya Perla
2015-03-20 10:28 ` [PATCH 2/3] be2net: restrict MODIFY_EQ_DELAY cmd to a max of 8 EQs Sathya Perla
2015-03-20 10:28 ` [PATCH 3/3] be2net: use PCI MMIO read instead of config read for errors Sathya Perla
2015-03-20 17:26 ` [PATCH 0/3] be2net: patch set David Miller
-- strict thread matches above, loose matches on Subject: below --
2015-08-05 7:27 Sathya Perla
2015-08-07 18:57 ` David Miller
2014-01-06 7:32 Sathya Perla
2014-01-06 18:10 ` 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=1426847305-23008-1-git-send-email-sathya.perla@emulex.com \
--to=sathya.perla@emulex.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).