| commit | de321a14da65a534da89a80dde949d0c6ff6316f | |
| author | Peter Hurley <peter@hurleysoftware.com> | |
| Tue, 29 Jan 2013 03:34:35 +0000 (28 22:34 -0500) | ||
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
| Wed, 30 Jan 2013 04:28:44 +0000 (29 23:28 -0500) | ||
| tree | 570391719343bd6bf7b868872805358fcc5eb2d4 | treesnapshot (tar.gz zip) |
| parent | 2b86216ba1d059b2609532ded9400f905013b376 | commitdiff |
staging/fwserial: Only reset port status for attached peers
When a port has been reserved in an attempt to connect to a peer
but that attempt does not succeed, releasing the port should not
reset the port line status. Although resetting is functionally
harmless, it can appear as if a remote peer dropped carrier to a
port it was not attached to (which can be confusing).
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
When a port has been reserved in an attempt to connect to a peer
but that attempt does not succeed, releasing the port should not
reset the port line status. Although resetting is functionally
harmless, it can appear as if a remote peer dropped carrier to a
port it was not attached to (which can be confusing).
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| drivers/staging/fwserial/fwserial.c | diffblobblamehistory |