From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: dougthompson@xmission.com
Cc: bluesmoke-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [PATCH] Remove unusued edac_reset_delay_period function
Date: Sat, 21 Jul 2007 14:28:42 +0300 [thread overview]
Message-ID: <200707211428.45973.caglar@pardus.org.tr> (raw)
Hi;
Following patch removes unused [1] edac_reset_delay_period function to silent
drivers/edac/edac_mc.c:334: warning: 'edac_reset_delay_period' defined but not used
compile warning.
[1]
caglar@zangetsu linux-2.6 $ grep edac_reset_delay_period * -r
drivers/edac/edac_mc.c: * edac_reset_delay_period
drivers/edac/edac_mc.c:static void edac_reset_delay_period(struct mem_ctl_info *mci, unsigned long value)
Signed-off-by: S.Çağlar Onur <caglar@pardus.org.tr>
drivers/edac/edac_mc.c | 17 -----------------
1 files changed, 0 insertions(+), 17 deletions(-)
diff --git a/drivers/edac/edac_mc.c b/drivers/edac/edac_mc.c
index 4471be3..c36a19a 100644
--- a/drivers/edac/edac_mc.c
+++ b/drivers/edac/edac_mc.c
@@ -327,23 +327,6 @@ static void edac_mc_workq_teardown(struct mem_ctl_info *mci)
}
}
-/*
- * edac_reset_delay_period
- */
-static void edac_reset_delay_period(struct mem_ctl_info *mci, unsigned long value)
-{
- /* cancel the current workq request */
- edac_mc_workq_teardown(mci);
-
- /* lock the list of devices for the new setup */
- mutex_lock(&mem_ctls_mutex);
-
- /* restart the workq request, with new delay value */
- edac_mc_workq_setup(mci, value);
-
- mutex_unlock(&mem_ctls_mutex);
-}
-
/* Return 0 on success, 1 on failure.
* Before calling this function, caller must
* assign a unique value to mci->mc_idx.
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
reply other threads:[~2007-07-21 11:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200707211428.45973.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=dougthompson@xmission.com \
--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