All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: linux-media@vger.kernel.org
Subject: Re: atomisp: drop from staging ?
Date: Mon, 30 Apr 2018 12:41:00 +0300	[thread overview]
Message-ID: <20180430094100.rbppnbpw5pnuoth4@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <20180429011837.68859797@alans-desktop>

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.

-- 
Regards,

Sakari Ailus
e-mail: sakari.ailus@iki.fi

  reply	other threads:[~2018-04-30  9:41 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 [this message]
2018-05-03  8:30   ` Sakari Ailus
2018-05-04 14:17     ` Mauro Carvalho Chehab
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=20180430094100.rbppnbpw5pnuoth4@valkosipuli.retiisi.org.uk \
    --to=sakari.ailus@iki.fi \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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 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.