All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: how get drm-intel-next into a stable kernel
Date: Thu, 5 Aug 2010 10:58:36 -0700	[thread overview]
Message-ID: <20100805175836.GA12571@kroah.com> (raw)
In-Reply-To: <20100805105409.35575e31@virtuousgeek.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

  reply	other threads:[~2010-08-05 17:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 15:38 how get drm-intel-next into a stable kernel Sergio Monteiro Basto
2010-08-05 17:54 ` Jesse Barnes
2010-08-05 17:58   ` Greg KH [this message]
2010-08-05 18:47     ` Timothy B. Terriberry
2010-08-05 19:03       ` Brice Goglin
2010-08-05 19:47         ` Timothy B. Terriberry
2010-08-05 20:57           ` Sergio Monteiro Basto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100805175836.GA12571@kroah.com \
    --to=greg@kroah.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.