From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 0/2] [media] tvp5150: use .registered callback to register entity and links
Date: Thu, 11 Aug 2016 22:31:35 +0300 [thread overview]
Message-ID: <57ACD297.1070408@linux.intel.com> (raw)
In-Reply-To: <1470932896-25843-1-git-send-email-javier@osg.samsung.com>
Javier Martinez Canillas wrote:
> Hello,
>
> Sakari pointed out in "[PATCH 2/8] [media] v4l2-async: call registered_async
> after subdev registration" [0] that the added .registered_async callback isn't
> needed since the v4l2 core already has an internal_ops .registered callback.
>
> I missed that there was already this when added the .registered_async callback,
> sorry about that.
>
> This small series convert the tvp5150 driver to use the proper .registered and
> remove .registered_async since isn't needed.
Thanks!
For both:
Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
--
Kind regards,
Sakari Ailus
sakari.ailus@linux.intel.com
next prev parent reply other threads:[~2016-08-11 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 16:28 [PATCH 0/2] [media] tvp5150: use .registered callback to register entity and links Javier Martinez Canillas
2016-08-11 16:28 ` [PATCH 1/2] [media] tvp5150: use sd internal ops .registered instead .registered_async Javier Martinez Canillas
2016-08-11 16:28 ` [PATCH 2/2] [media] v4l2-async: remove unneeded .registered_async callback Javier Martinez Canillas
2016-08-11 19:31 ` Sakari Ailus [this message]
2016-08-11 19:33 ` [PATCH 0/2] [media] tvp5150: use .registered callback to register entity and links Javier Martinez Canillas
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=57ACD297.1070408@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=javier@osg.samsung.com \
--cc=laurent.pinchart@ideasonboard.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