From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Subject: [PATCH 0/2] [media] tvp5150: use .registered callback to register entity and links
Date: Thu, 11 Aug 2016 12:28:14 -0400 [thread overview]
Message-ID: <1470932896-25843-1-git-send-email-javier@osg.samsung.com> (raw)
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.
[0]: https://lkml.org/lkml/2016/8/11/254
Best regards,
Javier
Javier Martinez Canillas (2):
[media] tvp5150: use sd internal ops .registered instead
.registered_async
[media] v4l2-async: remove unneeded .registered_async callback
drivers/media/i2c/tvp5150.c | 8 ++++++--
drivers/media/v4l2-core/v4l2-async.c | 7 -------
include/media/v4l2-subdev.h | 3 ---
3 files changed, 6 insertions(+), 12 deletions(-)
--
2.5.5
next reply other threads:[~2016-08-11 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 16:28 Javier Martinez Canillas [this message]
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 ` [PATCH 0/2] [media] tvp5150: use .registered callback to register entity and links Sakari Ailus
2016-08-11 19:33 ` 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=1470932896-25843-1-git-send-email-javier@osg.samsung.com \
--to=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 \
--cc=sakari.ailus@linux.intel.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®