From 67a814e9f9797570b520ca7499bc82684dc481a0 Mon Sep 17 00:00:00 2001 From: Shaun Ruffell Date: Thu, 2 Jun 2011 20:00:56 +0000 Subject: 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 Acked-by: Russ Meyerriecks git-svn-id: http://svn.asterisk.org/svn/dahdi/linux/trunk@9932 a0bf4364-ded3-4de4-8d8a-66a801d63aff --- drivers/dahdi/wct4xxp/base.c | 1 - 1 file changed, 1 deletion(-) (limited to 'drivers') diff --git a/drivers/dahdi/wct4xxp/base.c b/drivers/dahdi/wct4xxp/base.c index 68fe8b1..2233cdc 100644 --- a/drivers/dahdi/wct4xxp/base.c +++ b/drivers/dahdi/wct4xxp/base.c @@ -1737,7 +1737,6 @@ static int t4_clear_maint(struct dahdi_span *span) /* 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; -- cgit v1.2.3