From: Geliang Tang <geliangtang@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geliang Tang <geliangtang@gmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 11/12] [media] wl128x: use setup_timer
Date: Sun, 9 Apr 2017 09:34:07 +0800 [thread overview]
Message-ID: <51e22bc38526ec47c01030147761a873fac3e894.1490953290.git.geliangtang@gmail.com> (raw)
In-Reply-To: <77c0fb26d214e023a99afc948c71d6edd9284205.1490953290.git.geliangtang@gmail.com>
In-Reply-To: <77c0fb26d214e023a99afc948c71d6edd9284205.1490953290.git.geliangtang@gmail.com>
Use setup_timer() instead of init_timer() to simplify the code.
Signed-off-by: Geliang Tang <geliangtang@gmail.com>
---
drivers/media/radio/wl128x/fmdrv_common.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/media/radio/wl128x/fmdrv_common.c b/drivers/media/radio/wl128x/fmdrv_common.c
index 74a1b3e..588e2d6 100644
--- a/drivers/media/radio/wl128x/fmdrv_common.c
+++ b/drivers/media/radio/wl128x/fmdrv_common.c
@@ -1550,9 +1550,8 @@ int fmc_prepare(struct fmdev *fmdev)
atomic_set(&fmdev->tx_cnt, 1);
fmdev->resp_comp = NULL;
- init_timer(&fmdev->irq_info.timer);
- fmdev->irq_info.timer.function = &int_timeout_handler;
- fmdev->irq_info.timer.data = (unsigned long)fmdev;
+ setup_timer(&fmdev->irq_info.timer, &int_timeout_handler,
+ (unsigned long)fmdev);
/*TODO: add FM_STIC_EVENT later */
fmdev->irq_info.mask = FM_MAL_EVENT;
--
2.9.3
next prev parent reply other threads:[~2017-04-09 1:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 1:33 [PATCH 01/12] [media] saa7134: " Geliang Tang
2017-04-09 1:33 ` [PATCH 02/12] [media] saa7146: " Geliang Tang
2017-04-09 1:33 ` [PATCH 03/12] [media] bt8xx: " Geliang Tang
2017-04-09 1:34 ` [PATCH 04/12] [media] cx18: " Geliang Tang
2017-04-09 1:34 ` [PATCH 05/12] [media] ivtv: " Geliang Tang
2017-04-09 1:34 ` [PATCH 06/12] [media] netup_unidvb: " Geliang Tang
2017-04-09 1:34 ` [PATCH 07/12] [media] av7110: " Geliang Tang
2017-04-09 1:34 ` [PATCH 08/12] [media] fsl-viu: " Geliang Tang
2017-04-09 1:34 ` [PATCH 09/12] [media] s5p-mfc: " Geliang Tang
[not found] ` <CGME20170410083414epcas5p401f39ae110afbae34e0f2c6b53bd86a3@epcas5p4.samsung.com>
2017-04-10 8:33 ` Sylwester Nawrocki
2017-04-09 1:34 ` [PATCH 10/12] [media] c8sectpfe: " Geliang Tang
2017-04-09 1:34 ` Geliang Tang [this message]
2017-04-09 1:34 ` [PATCH 12/12] [media] imon: " Geliang Tang
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=51e22bc38526ec47c01030147761a873fac3e894.1490953290.git.geliangtang@gmail.com \
--to=geliangtang@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®