From: SeongJae Park <sj38.park@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 2/2] Remove CsrThreadHandle
Date: Tue, 23 Oct 2012 15:00:07 +0900 [thread overview]
Message-ID: <1350972007-5855-2-git-send-email-sj38.park@gmail.com> (raw)
In-Reply-To: <1350972007-5855-1-git-send-email-sj38.park@gmail.com>
CsrThreadHandle is typedef of struct CsrThread.
Some functions in csr_framework_ext.h use it as parameter.
But, nobody call them.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
drivers/staging/csr/csr_framework_ext.h | 49 -------------------------
drivers/staging/csr/csr_framework_ext_types.h | 2 -
2 files changed, 51 deletions(-)
diff --git a/drivers/staging/csr/csr_framework_ext.h b/drivers/staging/csr/csr_framework_ext.h
index 66973e9..16635a9 100644
--- a/drivers/staging/csr/csr_framework_ext.h
+++ b/drivers/staging/csr/csr_framework_ext.h
@@ -181,55 +181,6 @@ void CsrGlobalMutexUnlock(void);
/*----------------------------------------------------------------------------*
* NAME
- * CsrThreadCreate
- *
- * DESCRIPTION
- * Create thread function and return a handle to the created thread.
- *
- * RETURNS
- * Possible values:
- * CSR_RESULT_SUCCESS in case of success
- * CSR_FE_RESULT_NO_MORE_THREADS in case of out of thread resources
- * CSR_FE_RESULT_INVALID_POINTER in case one of the supplied pointers is invalid
- *
- *----------------------------------------------------------------------------*/
-CsrResult CsrThreadCreate(void (*threadFunction)(void *pointer), void *pointer,
- u32 stackSize, u16 priority,
- const char *threadName, CsrThreadHandle *threadHandle);
-
-/*----------------------------------------------------------------------------*
- * NAME
- * CsrThreadGetHandle
- *
- * DESCRIPTION
- * Return thread handle of calling thread.
- *
- * RETURNS
- * Possible values:
- * CSR_RESULT_SUCCESS in case of success
- * CSR_FE_RESULT_INVALID_POINTER in case the threadHandle pointer is invalid
- *
- *----------------------------------------------------------------------------*/
-CsrResult CsrThreadGetHandle(CsrThreadHandle *threadHandle);
-
-/*----------------------------------------------------------------------------*
- * NAME
- * CsrThreadEqual
- *
- * DESCRIPTION
- * Compare thread handles
- *
- * RETURNS
- * Possible values:
- * CSR_RESULT_SUCCESS in case thread handles are identical
- * CSR_FE_RESULT_INVALID_POINTER in case either threadHandle pointer is invalid
- * CSR_RESULT_FAILURE otherwise
- *
- *----------------------------------------------------------------------------*/
-CsrResult CsrThreadEqual(CsrThreadHandle *threadHandle1, CsrThreadHandle *threadHandle2);
-
-/*----------------------------------------------------------------------------*
- * NAME
* CsrThreadSleep
*
* DESCRIPTION
diff --git a/drivers/staging/csr/csr_framework_ext_types.h b/drivers/staging/csr/csr_framework_ext_types.h
index 2bf854a..cd1f877 100644
--- a/drivers/staging/csr/csr_framework_ext_types.h
+++ b/drivers/staging/csr/csr_framework_ext_types.h
@@ -32,7 +32,6 @@ struct CsrEvent {
typedef struct CsrEvent CsrEventHandle;
typedef struct semaphore CsrMutexHandle;
-typedef struct CsrThread CsrThreadHandle;
#else /* __KERNEL __ */
@@ -44,7 +43,6 @@ struct CsrEvent {
typedef struct CsrEvent CsrEventHandle;
typedef pthread_mutex_t CsrMutexHandle;
-typedef pthread_t CsrThreadHandle;
#endif /* __KERNEL__ */
--
1.7.9.5
prev parent reply other threads:[~2012-10-23 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 6:00 [PATCH 1/2] Remove struct CsrThread SeongJae Park
2012-10-23 6:00 ` SeongJae Park [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1350972007-5855-2-git-send-email-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome