From: Geliang Tang <geliangtang@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Geliang Tang <geliangtang@gmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 08/12] [media] fsl-viu: use setup_timer
Date: Sun, 9 Apr 2017 09:34:04 +0800 [thread overview]
Message-ID: <918f608faa071c2ff1b77d2642369555b03cb61c.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/platform/fsl-viu.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/media/platform/fsl-viu.c b/drivers/media/platform/fsl-viu.c
index ae8c6b3..97e164b 100644
--- a/drivers/media/platform/fsl-viu.c
+++ b/drivers/media/platform/fsl-viu.c
@@ -1466,9 +1466,8 @@ static int viu_of_probe(struct platform_device *op)
viu_dev->decoder = v4l2_i2c_new_subdev(&viu_dev->v4l2_dev, ad,
"saa7113", VIU_VIDEO_DECODER_ADDR, NULL);
- viu_dev->vidq.timeout.function = viu_vid_timeout;
- viu_dev->vidq.timeout.data = (unsigned long)viu_dev;
- init_timer(&viu_dev->vidq.timeout);
+ setup_timer(&viu_dev->vidq.timeout, viu_vid_timeout,
+ (unsigned long)viu_dev);
viu_dev->std = V4L2_STD_NTSC_M;
viu_dev->first = 1;
--
2.9.3
next prev parent reply other threads:[~2017-04-09 1:36 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 ` Geliang Tang [this message]
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 ` [PATCH 11/12] [media] wl128x: " Geliang Tang
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=918f608faa071c2ff1b77d2642369555b03cb61c.1490953290.git.geliangtang@gmail.com \
--to=geliangtang@gmail.com \
--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®