linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: linux-media@vger.kernel.org, Jacopo Mondi <jacopo+renesas@jmondi.org>
Subject: Re: [PATCH 0/8] Remove obsolete soc_camera drivers
Date: Fri, 18 Jan 2019 11:06:57 +0200	[thread overview]
Message-ID: <20190118090656.rdsx7jrfnvmtp3o4@kekkonen.localdomain> (raw)
In-Reply-To: <738da2a6-e8a3-c09b-d9b8-4489eeb4f46a@xs4all.nl>

On Fri, Jan 18, 2019 at 09:58:43AM +0100, Hans Verkuil wrote:
> On 1/18/19 9:56 AM, Sakari Ailus wrote:
> > On Thu, Jan 17, 2019 at 05:17:54PM +0100, hverkuil-cisco@xs4all.nl wrote:
> >> From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
> >>
> >> The soc_mt9t112, soc_ov772x and soc_tw9910 drivers now have
> >> non-soc-camera replacements, so those three drivers can be
> >> removed.
> >>
> >> The soc_camera sh_mobile_ceu_camera platform driver also has
> >> a non-soc-camera replacement, so remove this driver as well.
> >>
> >> This driver was also the last driver that used soc_scale_crop,
> >> so remove that too. Finally remove the test soc_camera_platform
> >> driver. There will be no more soc_camera platform drivers, so this
> >> platform template driver serves no purpose anymore.
> > 
> > For the set:
> > 
> > Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > 
> > Are you planning to move the rest of the drivers to staging and depend on
> > BROKEN, or should I do that?
> > 
> 
> Can you do that?

Certainly. I just want to make sure we don't both do it. :-)

-- 
Sakari Ailus
sakari.ailus@linux.intel.com

      reply	other threads:[~2019-01-18  9:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 16:17 [PATCH 0/8] Remove obsolete soc_camera drivers hverkuil-cisco
2019-01-17 16:17 ` [PATCH 1/8] media: tw9910: Unregister subdevice with v4l2-async hverkuil-cisco
2019-01-17 16:17 ` [PATCH 2/8] soc_mt9t112: remove obsolete sensor driver hverkuil-cisco
2019-01-17 16:17 ` [PATCH 3/8] soc_ov772x: " hverkuil-cisco
2019-01-17 16:17 ` [PATCH 4/8] tw9910.h: remove obsolete soc_camera.h include hverkuil-cisco
2019-01-17 16:17 ` [PATCH 5/8] soc_tw9910: remove obsolete sensor driver hverkuil-cisco
2019-01-17 16:18 ` [PATCH 6/8] sh_mobile_ceu_camera: remove obsolete soc_camera driver hverkuil-cisco
2019-01-17 16:18 ` [PATCH 7/8] soc_camera/soc_scale_crop: drop this unused code hverkuil-cisco
2019-01-17 16:18 ` [PATCH 8/8] soc_camera_platform: remove obsolete soc_camera test driver hverkuil-cisco
2019-01-18  8:56 ` [PATCH 0/8] Remove obsolete soc_camera drivers Sakari Ailus
2019-01-18  8:58   ` Hans Verkuil
2019-01-18  9:06     ` Sakari Ailus [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=20190118090656.rdsx7jrfnvmtp3o4@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jacopo+renesas@jmondi.org \
    --cc=linux-media@vger.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;
as well as URLs for NNTP newsgroup(s).