From: Adrian Bunk <bunk@stusta.de>
To: george@mvista.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC: 2.6 patch] kernel/posix-timers.c: remove do_posix_clock_notimer_create()
Date: Sat, 7 Jan 2006 23:32:10 +0100 [thread overview]
Message-ID: <20060107223210.GB3774@stusta.de> (raw)
Is there any reason for this function that is neither used nor has any
real contents?
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
include/linux/posix-timers.h | 1 -
kernel/posix-timers.c | 6 ------
2 files changed, 7 deletions(-)
--- linux-2.6.15-mm2-full/include/linux/posix-timers.h.old 2006-01-07 23:13:08.000000000 +0100
+++ linux-2.6.15-mm2-full/include/linux/posix-timers.h 2006-01-07 23:13:17.000000000 +0100
@@ -84,7 +84,6 @@
void register_posix_clock(const clockid_t clock_id, struct k_clock *new_clock);
/* error handlers for timer_create, nanosleep and settime */
-int do_posix_clock_notimer_create(struct k_itimer *timer);
int do_posix_clock_nonanosleep(const clockid_t, int flags, struct timespec *,
struct timespec __user *);
int do_posix_clock_nosettime(const clockid_t, struct timespec *tp);
--- linux-2.6.15-mm2-full/kernel/posix-timers.c.old 2006-01-07 23:13:25.000000000 +0100
+++ linux-2.6.15-mm2-full/kernel/posix-timers.c 2006-01-07 23:13:30.000000000 +0100
@@ -875,12 +875,6 @@
}
EXPORT_SYMBOL_GPL(do_posix_clock_nosettime);
-int do_posix_clock_notimer_create(struct k_itimer *timer)
-{
- return -EINVAL;
-}
-EXPORT_SYMBOL_GPL(do_posix_clock_notimer_create);
-
int do_posix_clock_nonanosleep(const clockid_t clock, int flags,
struct timespec *t, struct timespec __user *r)
{
next reply other threads:[~2006-01-07 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 22:32 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-19 23:33 [RFC: 2.6 patch] kernel/posix-timers.c: remove do_posix_clock_notimer_create() Adrian Bunk
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=20060107223210.GB3774@stusta.de \
--to=bunk@stusta.de \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.