All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-media <linux-media@vger.kernel.org>,
	Sakari Ailus <sakari.ailus@iki.fi>
Subject: Re: [PATCH] soc_camera/omap1: move to staging in preparation for removal
Date: Tue, 23 Feb 2016 17:09:53 +0100	[thread overview]
Message-ID: <56CC8451.5080909@xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.1602231701380.17650@axis700.grange>

On 02/23/2016 05:03 PM, Guennadi Liakhovetski wrote:
> On Tue, 23 Feb 2016, Hans Verkuil wrote:
> 
>> On 02/23/2016 04:05 PM, Guennadi Liakhovetski wrote:
>>> On Tue, 23 Feb 2016, Hans Verkuil wrote:
>>>
>>>> On 02/23/16 15:55, Guennadi Liakhovetski wrote:
>>>>> Hi Hans,
>>>>>
>>>>> On Tue, 23 Feb 2016, Hans Verkuil wrote:
>>>>>
>>>>>> This driver is deprecated: it needs to be converted to vb2 and
>>>>>> it should become a stand-alone driver instead of using the
>>>>>> soc-camera framework.
>>>>>>
>>>>>> Unless someone is willing to take this on (unlikely with such
>>>>>> ancient hardware) it is going to be removed from the kernel
>>>>>> soon.
>>>>>>
>>>>>> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
>>>>>
>>>>> I guess I won't be pulling this through my tree, right?
>>>>
>>>> Right.
>>>>
>>>>>
>>>>> Acked-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
>>>>
>>>> Thanks!
>>>>
>>>> This one was easy.
>>>
>>> mx2, mx3 should be easy too?
>>
>> Sure. Are you certain these can be deprecated? I haven't heard
>> anything regarding the status of these driver. You probably know that
>> best.
>>
>> If you give me the go ahead, then I'll prepare patches for these to
>> move them to staging.
> 
> I asked pengutronix guys, they don't care about them any more. We had 
> someone from freescale on CC in the original discussion, they didn't 
> report back either, so... Up to you really, I'd put the probability of 
> someone coming forward with a strong enough case to keep them at 4% :-) Is 
> it good enough for you to prepare that patch?

Yes, that's good enough. It's not as if we remove it right away, it'll be
in staging for a while.

Thanks for the info,

	Hans


      reply	other threads:[~2016-02-23 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 12:13 [PATCH] soc_camera/omap1: move to staging in preparation for removal Hans Verkuil
2016-02-23 14:55 ` Guennadi Liakhovetski
2016-02-23 14:59   ` Hans Verkuil
2016-02-23 15:05     ` Guennadi Liakhovetski
2016-02-23 15:56       ` Hans Verkuil
2016-02-23 16:03         ` Guennadi Liakhovetski
2016-02-23 16:09           ` Hans Verkuil [this message]

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=56CC8451.5080909@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.