linux-kernel - Re: [GIT PATCH] STAGING patches for .39

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, 16 Mar 2011 17:28:18 -0700
From:	Greg KH <greg@...ah.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, devel@...uxdriverproject.org
Subject: Re: [GIT PATCH] STAGING patches for .39

On Wed, Mar 16, 2011 at 05:19:47PM -0700, Linus Torvalds wrote:
> On Wed, Mar 16, 2011 at 2:03 PM, Greg KH <greg@...ah.com> wrote:
> > Here is the big staging tree merge for .39
> 
> So I try to compile all the staging drivers every once in a while.
> 
> This time I gave up even trying. After the GMA500 driver didn't
> compile (due to some crazy patch to dri_pci_init() that changes it to
> a calling convention that it has never had), there was another file
> that spewed out about five thousand lines of error/warning messages.
> 
> Aren't those things supposed to at least compile? What's going on?

The gma500 driver will not build until you pull the drm tree into yours
as that is an api dependancy it needs.  I didn't think you build staging
drivers, so I didn't think I needed to call this one out.  I was wrong :)

As for the others, I don't know of any build problems, what one did you
have a problem with?

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/