bfdd: Do not explicitly set the thread pointer to NULL

FRR should only ever use the appropriate THREAD_ON/THREAD_OFF
semantics.  This is espacially true for the functions we
end up calling the thread for.

Signed-off-by: Donatas Abraitis <donatas.abraitis@gmail.com>

diff --git a/bfdd/control.c b/bfdd/control.c
index 4929bf1998478456d28a36f1f45e7986ad4c129a..e772aadfc41bc9992585c471e7340aed09f146b2 100644 (file)
--- a/bfdd/control.c
+++ b/bfdd/control.c
@@ -167,7 +167,6 @@ int control_accept(struct thread *t)
 
        control_new(csock);
 
-       bglobal.bg_csockev = NULL;
        thread_add_read(master, control_accept, NULL, sd, &bglobal.bg_csockev);
 
        return 0;