[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131130162023.GB15077@kroah.com>
Date: Sat, 30 Nov 2013 08:20:23 -0800
From: Greg KH <gregkh@...uxfoundation.org>
To: Ivajlo Dimitrov <ivo.g.dimitrov.75@...il.com>
Cc: Ивайло Димитров
<freemangordon@....bg>, pali.rohar@...il.com, sre@...g0.de,
pavel@....cz, omar.ramirez@...itl.com, tony@...mide.com,
felipe.contreras@...il.com, s-anna@...com, nm@...com,
ohad@...ery.com, stable@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: Staging: tidspbridge: disable driver
On Sat, Nov 30, 2013 at 11:58:23AM +0200, Ivajlo Dimitrov wrote:
> Hi,
>
> (re-sending in plain text, sorry for the noise)
>
> commit
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=930ba4a374b96560ef9fde2145cdc454a164ddcc
> disables tidspbridge driver for the reasons it has a security bug and there
> is no active maintainer.
> I was following the development of that driver for a bit and my impression
> was that the reason it is
> still in staging is this
> http://www.spinics.net/lists/linux-omap/msg84115.html . And as dmtimer
> driver is on its way to be merged upstream(or was it already merged?) I was
> planning to work on
> tidspbridge driver to fix it and send the patches. I also have a couple of
> another small patches
> ready to be send.
> However, could you elaborate on the "security bug" so I can try to fix it
> and send the patch?
> Also, what needs to be done for the tidspdriver to get out of staging as it
> seems that what I
> though initially is incorrect.
There is also the very long TODO list in drivers/staging/tidspbridge/
What is the progression on that?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists