Searched hist:fe7cd2bfdac4d8739bc8665eef040e668e6b428f (Results 1 – 2 of 2) sorted by relevance
/linux/include/linux/qed/ |
H A D | qed_if.h | diff fe7cd2bfdac4d8739bc8665eef040e668e6b428f Fri Apr 22 07:41:03 CEST 2016 Yuval Mintz <Yuval.Mintz@qlogic.com> qed*: Conditions for changing link
There's some inconsistency in current logic determining whether the link settings of a given interface can be changed; I.e., in all modes other than the so-called `deault' mode the interfaces are forbidden from changing the configuration - but even this rule is not applied to all user APIs that may change the configuration.
Instead, let the core-module [qed] decide whether an interface can change the configuration by supporting a new API function. We also revise the current rule, allowing all interfaces to change their configurations while laying the infrastructure for future modes where an interface would be blocked from making such a configuration.
Signed-off-by: Yuval Mintz <Yuval.Mintz@qlogic.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
/linux/drivers/net/ethernet/qlogic/qed/ |
H A D | qed_main.c | diff fe7cd2bfdac4d8739bc8665eef040e668e6b428f Fri Apr 22 07:41:03 CEST 2016 Yuval Mintz <Yuval.Mintz@qlogic.com> qed*: Conditions for changing link
There's some inconsistency in current logic determining whether the link settings of a given interface can be changed; I.e., in all modes other than the so-called `deault' mode the interfaces are forbidden from changing the configuration - but even this rule is not applied to all user APIs that may change the configuration.
Instead, let the core-module [qed] decide whether an interface can change the configuration by supporting a new API function. We also revise the current rule, allowing all interfaces to change their configurations while laying the infrastructure for future modes where an interface would be blocked from making such a configuration.
Signed-off-by: Yuval Mintz <Yuval.Mintz@qlogic.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|