From: "tip-bot2 for YueHaibing" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: YueHaibing <yuehaibing@huawei.com>,
Thomas Gleixner <tglx@linutronix.de>, x86 <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [tip: timers/urgent] timers: Remove unused inline funtion debug_timer_free()
Date: Mon, 26 Oct 2020 10:40:18 -0000 [thread overview]
Message-ID: <160370881802.397.15234178664001900654.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20200909134749.32300-1-yuehaibing@huawei.com>
The following commit has been merged into the timers/urgent branch of tip:
Commit-ID: 9010e3876e1c3f7b1c3769bee519d6a871589aca
Gitweb: https://git.kernel.org/tip/9010e3876e1c3f7b1c3769bee519d6a871589aca
Author: YueHaibing <yuehaibing@huawei.com>
AuthorDate: Wed, 09 Sep 2020 21:47:49 +08:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Mon, 26 Oct 2020 11:39:21 +01:00
timers: Remove unused inline funtion debug_timer_free()
There is no caller in tree, remove it.
Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20200909134749.32300-1-yuehaibing@huawei.com
---
kernel/time/timer.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/kernel/time/timer.c b/kernel/time/timer.c
index de37e33..c3ad64f 100644
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
@@ -732,11 +732,6 @@ static inline void debug_timer_deactivate(struct timer_list *timer)
debug_object_deactivate(timer, &timer_debug_descr);
}
-static inline void debug_timer_free(struct timer_list *timer)
-{
- debug_object_free(timer, &timer_debug_descr);
-}
-
static inline void debug_timer_assert_init(struct timer_list *timer)
{
debug_object_assert_init(timer, &timer_debug_descr);
prev parent reply other threads:[~2020-10-26 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 13:47 [PATCH -next] " YueHaibing
2020-10-26 10:40 ` tip-bot2 for YueHaibing [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=160370881802.397.15234178664001900654.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yuehaibing@huawei.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
all inboxes | Powered by JetHome®