public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
	linux-media@vger.kernel.org, andriy.shevchenko@intel.com
Subject: Re: atomisp: drop from staging ?
Date: Fri, 4 May 2018 11:17:30 -0300	[thread overview]
Message-ID: <20180504111730.5ef8bdf8@vento.lan> (raw)
In-Reply-To: <20180503083049.nidmolfegklwnsqr@valkosipuli.retiisi.org.uk>

Em Thu, 3 May 2018 11:30:50 +0300
Sakari Ailus <sakari.ailus@iki.fi> escreveu:

> On Mon, Apr 30, 2018 at 12:41:00PM +0300, Sakari Ailus wrote:
> > Hi Alan,
> > 
> > On Sun, Apr 29, 2018 at 01:18:37AM +0100, Alan Cox wrote:  
> > > 
> > > I think this is going to be the best option. When I started cleaning up
> > > the atomisp code I had time to work on it. Then spectre/meltdown
> > > happened (which btw is why the updating suddenly and mysteriously stopped
> > > last summer).
> > > 
> > > I no longer have time to work on it and it's becoming evident that the
> > > world of speculative side channel is going to be mean that I am
> > > not going to get time in the forseeable future despite me trying to find
> > > space to get back into atomisp cleaning up. It sucks because we made some
> > > good initial progress but shit happens.
> > > 
> > > There are at this point (unsurprisngly ;)) no other volunteers I can
> > > find crazy enough to take this on.  
> > 
> > The driver has been in the staging tree for quite some time now and is a
> > regular target of cleanup patches but little has been done to address the
> > growing list of entries in the associated TODO file to get it out of
> > staging. Beyond this, I don't have the hardware but as far as I understand,
> > the driver is not functional in its current state.
> > 
> > I agree with removing the driver. It can always be brought back if someone
> > wishes to continue working it.
> > 
> > I can send patches to remove it.  
> 
> The patch didn't make it to the list likely because it was too big --- even
> with -D option to git format-patch!
> 
> It's here:
> 
> <URL:https://git.linuxtv.org/sailus/media_tree.git/log/?h=atomisp-no-more>

I really hate remove things like that, but atomisp is on real bad shape.
I'm wandering if at least the sensor drivers could be converted before
dropping it.

That's said, I don't have atomisp hardware either, and, even if I had,
I probably won't have enough time to fix it. So, if you all won't be
able to do any work on it any time soon, and that's what you want
for now, I'm ok with removing it.

Sakari,

Please send me a pull request with the driver removal patch and I'll
apply it.


Thanks,
Mauro

  reply	other threads:[~2018-05-04 14:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29  0:18 atomisp: drop from staging ? Alan Cox
2018-04-30  9:41 ` Sakari Ailus
2018-05-03  8:30   ` Sakari Ailus
2018-05-04 14:17     ` Mauro Carvalho Chehab [this message]
2018-05-07 11:38       ` Sakari Ailus

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=20180504111730.5ef8bdf8@vento.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox