[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30da8426b86a45cff8556daa72dc82457044c006.1362133319.git.michail.kurachkin@promwad.com>
Date: Fri, 1 Mar 2013 14:03:37 +0300
From: Michail Kurachkin <michail.kurachkin@...mwad.com>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Kuten Ivan <Ivan.Kuten@...mwad.com>,
"benavi@...vell.com" <benavi@...vell.com>,
Palstsiuk Viktar <Viktar.Palstsiuk@...mwad.com>,
Dmitriy Gorokh <dmitriy.gorokh@...mwad.com>,
Oliver Neukum <oneukum@...e.de>,
Ryan Mallon <rmallon@...il.com>
CC: Michail Kurachkin <michail.kurachkin@...mwad.com>
Subject: [PATCH v2 10/11] staging: add issuses in TODO
Signed-off-by: Michail Kurachkin <michail.kurachkin@...mwad.com>
---
drivers/staging/si3226x/TODO | 15 +++++++++++++--
1 files changed, 13 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/si3226x/TODO b/drivers/staging/si3226x/TODO
index b2cb27e..8d81465 100644
--- a/drivers/staging/si3226x/TODO
+++ b/drivers/staging/si3226x/TODO
@@ -1,8 +1,19 @@
+Needed to be done to get the code out of the staging tree:
1) mutex_lock(&slic_chr_dev_lock);
This locking is very heavy handed and should be reworked
-2) SLIC driver works unstable when compiled as module, loaded, then unloaded and finally reloaded again.
+2) SLIC driver works unstable when compiled as module,
+loaded, then unloaded and finally reloaded again.
-3) Current version of Si3226x SLIC driver is limited. It implements only base functionality such as Answer, Hangup, receive DTMF, send DTMF, send Caller ID.
+3) ensure stability of current driver, define several test scenarios
+4) Current version of Si3226x SLIC driver is limited. It implements
+only base functionality such as Answer, Hangup, receive DTMF,
+send DTMF, send Caller ID.
+
+
+Mainteiners:
+Michail Kurachkin <Michail.Kurachkin@...mwad.com> <stelhs@...dex.ru>
+Ivan Kuten <ivan.kuten@...mwad.com>
+Promwad company <info@...mwad.com>
--
1.7.5.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists