From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: greg@kroah.com, mark.a.allyn@intel.com, linux-kernel@vger.kernel.org
Subject: [PATCH 05/12] sep: clean up caller_id function
Date: Wed, 24 Nov 2010 19:34:25 +0000 [thread overview]
Message-ID: <20101124193419.16425.37036.stgit@bob.linux.org.uk> (raw)
In-Reply-To: <20101124192136.16425.49994.stgit@bob.linux.org.uk>
From: Alan Cox <alan@linux.intel.com>
This is called on a kmalloc/memset object. Remove everything that isn't a
set to zero
Oh look 8)
Signed-off-by: Alan Cox <alan@linux.intel.com>
---
drivers/staging/sep/sep_driver.c | 42 --------------------------------------
1 files changed, 0 insertions(+), 42 deletions(-)
diff --git a/drivers/staging/sep/sep_driver.c b/drivers/staging/sep/sep_driver.c
index 38b2db4..c98cb9b 100644
--- a/drivers/staging/sep/sep_driver.c
+++ b/drivers/staging/sep/sep_driver.c
@@ -934,38 +934,6 @@ static unsigned long sep_set_time(struct sep_device *sep)
}
/**
- * sep_init_caller_id - initializes the caller id functionality
- * @sep: pointer to struct sep_device
- */
-static int sep_init_caller_id(struct sep_device *sep)
-{
- int counter;
-
- dev_dbg(&sep->pdev->dev,
- "sep_init_caller_id start\n");
-
- /**
- * init caller id table
- * note that locking is not needed here as this function is
- * called prior to registering the device file
- */
- for (counter = 0; counter < SEP_CALLER_ID_TABLE_NUM_ENTRIES; counter++)
- sep->caller_id_table[counter].pid = 0;
-
-
- /* init access flag */
- sep->singleton_access_flag = 0;
-
- dev_dbg(&sep->pdev->dev,
- "caller id table init finished\n");
-
- dev_dbg(&sep->pdev->dev,
- "sep_init_caller_id end\n");
-
- return 0;
-}
-
-/**
* sep_set_caller_id_handler - inserts the data into the caller id table
* note that this function does fall under the ioctl lock
* @sep: sep device
@@ -4056,16 +4024,6 @@ static int __init sep_init(void)
mutex_init(&sep->sep_mutex);
mutex_init(&sep->ioctl_mutex);
- if (sep->mrst == 0) {
- ret_val = sep_init_caller_id(sep);
- if (ret_val) {
- dev_warn(&sep->pdev->dev,
- "cant init caller id\n");
- goto end_function_unregister_pci;
- }
-
- }
-
/* new chip requires share area reconfigure */
if (sep->pdev->revision == 4) { /* only for new chip */
ret_val = sep_reconfig_shared_area(sep);
next prev parent reply other threads:[~2010-11-24 19:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 19:23 [PATCH 00/12] SEP cleanups Alan Cox
2010-11-24 19:33 ` [PATCH 01/12] sep: minimal fix for wrong include Alan Cox
2010-11-24 19:33 ` [PATCH 02/12] sep: handle the rar definition stuff in the header Alan Cox
2010-11-24 19:33 ` [PATCH 03/12] sep: handle the memrar stuff in the headers Alan Cox
2010-11-24 19:34 ` [PATCH 04/12] sep: netlink - what netlink Alan Cox
2010-11-24 19:34 ` Alan Cox [this message]
2010-11-24 19:34 ` [PATCH 06/12] sep: Fix the kernel-doc in SEP Alan Cox
2010-11-24 19:38 ` [PATCH 07/12] sep: clean up some of the obvious sillies Alan Cox
2010-11-24 19:38 ` [PATCH 08/12] sep: Use kzalloc when needed Alan Cox
2010-11-24 19:38 ` [PATCH 09/12] sep: Make SEP consistent Alan Cox
2010-11-24 19:38 ` [PATCH 10/12] sep: cant is an angular inclination Alan Cox
2010-11-24 19:39 ` [PATCH 11/12] sep: clean up a couple of spots missed in pass one Alan Cox
2010-11-24 19:39 ` [PATCH 12/12] sep: Fix crash if a device is not found Alan Cox
2010-11-24 20:18 ` [PATCH 00/12] SEP cleanups Randy Dunlap
2010-11-24 22:19 ` Alan Cox
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=20101124193419.16425.37036.stgit@bob.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.a.allyn@intel.com \
/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