linux-kernel - Re: doubt about sm7xxfb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 11 Feb 2015 14:33:51 +0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: doubt about sm7xxfb

On Wed, Feb 11, 2015 at 11:58:18AM +0530, Sudip Mukherjee wrote:
> On Wed, Feb 11, 2015 at 12:36:36PM +0800, Greg Kroah-Hartman wrote:
> > On Tue, Feb 10, 2015 at 07:37:47PM +0530, Sudip Mukherjee wrote:
> > > Hi Greg,
> > > we have this sm7xxfb in drivers/staging now which is supporting SM710,
> > > SM712, SM721 and SM722. I am also working on another new hardware
> > > SM750, which will be ready for staging in next 1 -2 weeks.
> > > this SM750 is entirely different hardware and these two drivers will
> > > have nothing in common.
> > 
> > Then make a new driver!
> ok, but then won't the name sm7xxfb will be misleading?

Sure, but really, who cares :)

> > But why would a new driver go into staging?  Anything new you create
> > should just go into the "correct" part of the kernel.  Don't waste your
> > time on staging.
> 
> this code has been given to me by Silicon Motion, and will require a
> few changes before it can be used with current kernel version. And to
> merge it into video/fbdev it will require many changes and cleanups.
> But to be frank this will have much less work to do compared to
> sm7xxfb, but as this is not part of my dayjob i can not give my full
> time to it. So I was thinking of staging.

Ok, that makes sense, I was thinking this was a "new" driver, instead of
a vendor driver crud.

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/