All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"yinghai@kernel.org" <yinghai@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@suse.de>,
	"lkml20101129@newton.leun.net" <lkml20101129@newton.leun.net>,
	stable kernel team <stable@kernel.org>
Subject: Re: [PATCH urgent] x86: Save cr4 to mmu_cr4_features at boot time
Date: Fri, 1 Apr 2011 21:08:12 +0200	[thread overview]
Message-ID: <20110401190812.GA16830@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.1104011212070.16492@kaball-desktop>


* Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:

> P.S.
>
> I asked for a backport of e5f15b45ddf3afa2bbbb10c7ea34fb32b6de0a0e to the 
> stable trees because I forgot to add "CC stable@kernel.org" to the commit 
> message and this commit is needed to fix a critical crash on boot on xen.

You are displaying a dangerously amateurish attitude towards quality control 
and you clealy have no idea what it takes to push fixes into -stable.

You forwarded a brand-new, visibly dangerous native kernel commit to -stable 
without Cc:-ing the maintainers and you have caused a native kernel regression 
that way. You are not maintaining the code in question and you have not 
committed the patch in question.

-stable team, please revert this commit. The whole issue obviously needs more 
testing and we'll forward a proper fix once it's available and tested.

	Ingo

  parent reply	other threads:[~2011-04-01 19:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 16:38 [PATCH urgent] x86: Save cr4 to mmu_cr4_features at boot time Stefano Stabellini
2011-04-01  6:23 ` Ingo Molnar
2011-04-01 11:30   ` Stefano Stabellini
2011-04-01 18:51     ` H. Peter Anvin
2011-04-01 19:08     ` Ingo Molnar [this message]
2011-04-01 20:59       ` [stable] " Greg KH
2011-04-01 22:57       ` Stefano Stabellini
2011-04-04 15:11         ` Ingo Molnar
2011-04-04 15:47           ` Stefano Stabellini
2011-04-04 16:25             ` Ingo Molnar
2011-04-05  6:29               ` Rafael J. Wysocki
2011-04-05  6:37                 ` H. Peter Anvin
2011-04-05  6:43                   ` Rafael J. Wysocki
2011-04-05  6:55                     ` H. Peter Anvin
2011-04-05 23:47                     ` H. Peter Anvin
2011-04-06  4:34                       ` Rafael J. Wysocki
2011-04-06  4:45                         ` H. Peter Anvin
2011-04-11 23:04   ` Greg KH

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=20110401190812.GA16830@elte.hu \
    --to=mingo@elte.hu \
    --cc=gregkh@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml20101129@newton.leun.net \
    --cc=stable@kernel.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.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.