linux-kernel - Re: drivers/drm/i915 maintenance process

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:	Mon, 06 Jun 2011 16:24:46 -0700
From:	Keith Packard <keithp@...thp.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	dri-devel@...ts.freedesktop.org,
	"drivers\, Intel" <Intel-gfx@...ts.freedesktop.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: drivers/drm/i915 maintenance process

On Mon, 6 Jun 2011 13:36:18 -0700, Jesse Barnes <jbarnes@...tuousgeek.org> wrote:

> Can you keep drm-intel-next fairly up to date with respect to the fixes
> branch?  I.e. keep it a superset of drm-intel-fixes for the most part?

Yes, I wanted to do that now, but -fixes is not a fast-forward from
-next and I thought I shouldn't be doing rebases.

> In PCI-land, this means re-basing my -next tree periodically before the
> merge window opens (though not right before the merge window unless
> something unexpected happens, like a patch needing to be dropped; in
> that case I'll delay the merge window push a bit to allow for more
> testing).

If a rebase around -RC1 is reasonable, then I'll do that now and move
changes over to that.

-- 
keith.packard@...el.com

Content of type "application/pgp-signature" skipped