[dahdi-commits] sruffell: linux/trunk r9932 - /linux/trunk/drivers/dahdi/wct4xxp/base.c

[SVN commits to the DAHDI project]

Author: sruffell
Date: Thu Jun  2 15:00:56 2011
New Revision: 9932

URL: http://svnview.digium.com/svn/dahdi?view=rev&rev=9932
Log:
wct4xxp: Do not set maintstat in t4_clear_maint.

If we always set maintstat to DAHDI_MAINT_NONE, dahdi_base will lose
track of what it thinks the current state of the span is.

For example, if you run
$ dahdi_maint -s 1 --loopback localhost

When t4_clear_maint is called, the current maintenance mode state,
'maintstat', is set to DAHDI_MAINT_NONE. So the next time you call:

$ dahdi_maint -s 1 --loopback off

dahdi-base.c will believe that the user is trying to set the maintenance
state from DAHDI_MAINT_NONE to DAHDI_MAINT_NONE and will not actually do
anything.

Signed-off-by: Shaun Ruffell <sruffell at digium.com>
Acked-by: Russ Meyerriecks <rmeyerriecks at digium.com>

Modified:
    linux/trunk/drivers/dahdi/wct4xxp/base.c

Modified: linux/trunk/drivers/dahdi/wct4xxp/base.c
URL: http://svnview.digium.com/svn/dahdi/linux/trunk/drivers/dahdi/wct4xxp/base.c?view=diff&rev=9932&r1=9931&r2=9932
==============================================================================
--- linux/trunk/drivers/dahdi/wct4xxp/base.c (original)
+++ linux/trunk/drivers/dahdi/wct4xxp/base.c Thu Jun  2 15:00:56 2011
@@ -1737,7 +1737,6 @@
 	/* Clear loopup/loopdown signals on the line */
 	reg = __t4_framer_in(wc, span->offset, FMR5);
 	__t4_framer_out(wc, span->offset, FMR5, (reg & ~(FMR5_XLU | FMR5_XLD)));
-	span->maintstat = DAHDI_MAINT_NONE;
 
 	spin_unlock_irqrestore(&wc->reglock, flags);
 	span->mainttimer = 0;