diff options
| author | Somnath Kotur <somnath.kotur@emulex.com> | 2013-12-05 12:07:55 +0530 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2013-12-06 15:03:40 -0500 |
| commit | 4bebb56a6d50ca50a34048194877dca34f572f8f (patch) | |
| tree | d2a8e95cfa4af553885b57ca1c819fcb31ad1bbe /mm/rmap.c | |
| parent | d0b7da8afa079ffe018ab3e92879b7138977fc8f (diff) | |
be2net: Fix Lancer error recovery to distinguish FW download
The Firmware update would be detected by looking at the sliport_error1/
sliport_error2 register values(0x02/0x00). If its not a FW reset the current
messaging would take place. If the error is due to FW reset, log a message to
user that "Firmware update in progress" and also do not log sliport_status and
sliport_error register values.
Signed-off-by: Kalesh AP <kalesh.purayil@emulex.com>
Signed-off-by: Somnath Kotur <somnath.kotur@emulex.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'mm/rmap.c')
0 files changed, 0 insertions, 0 deletions