From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Andy Walls <awalls@md.metrocast.net>,
Hans Verkuil <hans.verkuil@cisco.com>,
"Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>
Cc: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Scott Jiang <scott.jiang.linux@gmail.com>,
Axel Lin <axel.lin@ingics.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 05/12] media/i2c/sr030pc30: Remove compat control ops
Date: Mon, 15 Jun 2015 13:51:12 +0200 [thread overview]
Message-ID: <557EBC30.6090902@samsung.com> (raw)
In-Reply-To: <557EA7A2.8060403@xs4all.nl>
Hi Hans,
On 15/06/15 12:23, Hans Verkuil wrote:
> Sylwester,
>
> Can you confirm that this is only used with bridge drivers that use the
> control framework? Actually, this driver isn't used by any bridge driver
> in the kernel tree, but it is probably in use by out-of-tree code.
>
> I'd like your Ack (or Nack) before I merge this.
>
> Note that eventually these legacy support ops will disappear once all
> bridge drivers in the kernel have been converted to the control framework.
This sensor driver is used on board type which has been scratched long time
ago, feel free to do any changes in this code.
Acked-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
--
Regards,
Sylwester
next prev parent reply other threads:[~2015-06-15 11:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 16:31 [PATCH 00/12] media/subdevices: Remove unused compat control ops Ricardo Ribalda Delgado
2015-06-12 16:31 ` [PATCH 01/12] media/i2c/adv7343: Remove " Ricardo Ribalda Delgado
2015-06-15 12:51 ` Lad, Prabhakar
2015-06-12 16:31 ` [PATCH 02/12] media/i2c/adv7393: " Ricardo Ribalda Delgado
2015-06-12 16:31 ` [PATCH 03/12] media/i2c/cs5345: " Ricardo Ribalda Delgado
2015-06-12 16:31 ` [PATCH 04/12] media/i2c/saa717x: " Ricardo Ribalda Delgado
2015-06-12 16:31 ` [PATCH 05/12] media/i2c/sr030pc30: " Ricardo Ribalda Delgado
2015-06-15 10:23 ` Hans Verkuil
2015-06-15 11:51 ` Sylwester Nawrocki [this message]
2015-06-12 16:31 ` [PATCH 06/12] media/i2c/tda7432: " Ricardo Ribalda Delgado
2015-06-12 16:31 ` [PATCH 07/12] media/i2c/tlv320aic23: " Ricardo Ribalda Delgado
2015-06-12 16:31 ` [PATCH 08/12] media/i2c/tvp514x: " Ricardo Ribalda Delgado
2015-06-15 12:51 ` Lad, Prabhakar
2015-06-12 16:31 ` [PATCH 09/12] media/i2c/tvp7002: " Ricardo Ribalda Delgado
2015-06-15 12:52 ` Lad, Prabhakar
2015-06-12 16:31 ` [PATCH 10/12] i2c/wm8739: " Ricardo Ribalda Delgado
2015-06-12 16:31 ` [PATCH 11/12] pci/ivtv/ivtv-gpio: " Ricardo Ribalda Delgado
2015-06-12 16:31 ` [PATCH 12/12] media/radio/saa7706h: " Ricardo Ribalda Delgado
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=557EBC30.6090902@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=awalls@md.metrocast.net \
--cc=axel.lin@ingics.com \
--cc=boris.brezillon@free-electrons.com \
--cc=g.liakhovetski@gmx.de \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=prabhakar.csengg@gmail.com \
--cc=ricardo.ribalda@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=scott.jiang.linux@gmail.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