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]

Message-ID: <AANLkTikEEDDFxZQtvV46JJRU1NAtiXh_N4onJ1jwKHaF@mail.gmail.com>
Date:	Wed, 16 Mar 2011 17:32:00 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Greg KH <greg@...ah.com>
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 5:28 PM, Greg KH <greg@...ah.com> wrote:
>>
>> 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 :)

I don't try to compile the staging tree all the time, but I do tend to
try to check it every once in a while. So yes, let me know if there
are dependencies.

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

The one with inifinite errors was vt6655.

It may be due to network layer changes. I had some other drivers with
conflicts. Maybe this one didn't have content conflicts, but ended up
having conflicts due to changed semantics etc.

                 Linus
--
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/