diff options
author | David S. Miller <davem@davemloft.net> | 2017-03-23 21:53:31 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-03-23 21:53:31 +0300 |
commit | 028ba8aad3f103011f0110b7d5857a1b4fdd0e8d (patch) | |
tree | 6743dd92fab93d2e7f18d957ed1697c416a28007 /net/bridge/br_fdb.c | |
parent | 4deece6c9fe69f396812a956f526d1cb43e9c0f0 (diff) | |
parent | dec26533ae5b00f3f15759bc195cae6fe89a1f42 (diff) | |
download | linux-028ba8aad3f103011f0110b7d5857a1b4fdd0e8d.tar.xz |
Merge branch 'qed-management-interaction-and-feature-changes'
Yuval Mintz says:
====================
qed: Management interaction & feature changes
All patches in this series either affect direct interaction with the
management firmware, or changes logic relating to some values retrieved
from it.
Patch #1 revises the basic logic for sending messages to the management
firmware and there completion, and is the most significant [at least
code-wise] of the bunch.
Patch #2 changes infrastrcure in a way that should better protect us form
mistakes leading to stack corruption such as was fixed in
bb4802428432 ("qed: Prevent stack corruption on MFW interaction").
Patch #3 corrects some update API endian issue [sent here as it would
create conflicts with #2, and because it's lack would create a rather
insignifcant problem].
Patch #4 removes some unnecessary logging, allowing cleaner forward
compatibility with future management firmware versions.
Patches #5, #6 slightly change the number of possible L2 queues in some
scenarios, leading to the possibility of having more queues / VFS.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bridge/br_fdb.c')
0 files changed, 0 insertions, 0 deletions