diff options
| author | Julian Wiedmann <jwi@linux.ibm.com> | 2018-06-29 19:45:54 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-06-30 21:19:48 +0900 |
| commit | d025da9eb1e48d3e5f2a2ff13ac5ac536ba4be43 (patch) | |
| tree | cf29e525b6b7740ca89aabed8abbdbe2f052f3a0 /drivers/atm | |
| parent | ce28867fd20c23cd769e78b4d619c4755bf71a1c (diff) | |
| download | talos-obmc-linux-d025da9eb1e48d3e5f2a2ff13ac5ac536ba4be43.tar.gz talos-obmc-linux-d025da9eb1e48d3e5f2a2ff13ac5ac536ba4be43.zip | |
s390/qeth: consistently re-enable device features
commit e830baa9c3f0 ("qeth: restore device features after recovery") and
commit ce3443564145 ("s390/qeth: rely on kernel for feature recovery")
made sure that the HW functions for device features get re-programmed
after recovery.
But we missed that the same handling is also required when a card is
first set offline (destroying all HW context), and then online again.
Fix this by moving the re-enable action out of the recovery-only path.
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/atm')
0 files changed, 0 insertions, 0 deletions
