linux-kernel - Re: [git pull] drm

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: <20091211013449.GC28962@bombadil.infradead.org>
Date:	Thu, 10 Dec 2009 20:34:49 -0500
From:	Kyle McMartin <kyle@...artin.ca>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	"C. Bergstr?m" <cbergstrom@...hscale.com>,
	linux-kernel@...r.kernel.org, dri-devel@...ts.sf.net
Subject: Re: [git pull] drm

On Thu, Dec 10, 2009 at 04:32:56PM -0800, Linus Torvalds wrote:
> > "patches welcome"
> 
> The problem is that I have never even heard a Red Hat or Fedora person 
> actually acknoledge that yes, they should be trying to upstream it.
> 
> Have Red Hat and Fedora just decided that "upstream first" simply doesn't 
> matter any more? Because quite frankly, that was kind of the feeling I 
> came away with from the Kernel summit.
> 

Well, given that none of the Fedora kernel people were able to attend
this year for a variety of reasons, this is an interesting revelation to
me, I wasn't aware I thought this.

I, for one, would very much like nouveau to be upstream. It would
certainly make my life easier not having to worry about subtlely
breaking graphics adapters I can't test whenever we rebase to new git
changes in the DRM. Thankfully Ben and Dave have been ninja at dealing
with it, otherwise I probably would have punted it by now.

> It's like they _want_ to keep it internal.
>

regards, Kyle

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