From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: how get drm-intel-next into a stable kernel Date: Thu, 5 Aug 2010 10:58:36 -0700 Message-ID: <20100805175836.GA12571@kroah.com> References: <1281022735.29410.6.camel@segulix> <20100805105409.35575e31@virtuousgeek.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from coco.kroah.org (kroah.org [198.145.64.141]) by gabe.freedesktop.org (Postfix) with ESMTP id 2478E9E762 for ; Thu, 5 Aug 2010 10:59:28 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20100805105409.35575e31@virtuousgeek.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Jesse Barnes Cc: intel-gfx List-Id: intel-gfx@lists.freedesktop.org On Thu, Aug 05, 2010 at 10:54:09AM -0700, Jesse Barnes wrote: > Longer answer: drm-intel-next bits are targeted at the next kernel > release. When important fixes from drm-intel-next land in Linus's tree, > you can request that they be back ported to the stable tree by sending a > note to stable@kernel.org with the commit id(s). They have to meet the > stable criteria though; I think the kernel has a doc on what makes > something eligible for stable inclusion. Yes we do, see the file, Documenation/stable_kernel_rules.txt thanks, greg k-h