mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Noonan <steven@uplinklabs.net>
Cc: Eero Nurkkala <ext-eero.nurkkala@nokia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Rik van Riel <riel@redhat.com>,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Greg KH <greg@kroah.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [BISECTED] "conservative" cpufreq governor broken
Date: Wed, 7 Oct 2009 13:15:47 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0910071306300.9428@localhost.localdomain> (raw)
In-Reply-To: <f488382f0910070403s4659869tf3729778ec0082a1@mail.gmail.com>

On Wed, 7 Oct 2009, Steven Noonan wrote:
> > Well, probably because the machine never switched to NOHZ :)
> >
> >> > Also, this fix should probably be passed on to Greg K. H. (so it goes
> >> > in 2.6.31-stable) as well as Ingo Molnar (so it goes into -tip, and
> >> > hopefully to Linus for 2.6.32). Both CC'd.
> >
> > Don't worry, it'll go the right way. No need to cc the world and some
> > more :)
> >
> 
> Sorry if it's not kosher. I was told that when dealing with a
> bisection you should CC:
> 1. those involved with a bisected patch (the Signed-off-by people),
> 2. those responsible for the affected subsystem (doing an author check
> via script[1]),
> 3. and those to whom a fix should be passed on to.
> 
> Any tips so I don't bug the wrong people (or too many people) in the future?

No worry. It's just Linus and Greg who got some extra mail into their
inbox. The flow is that the patch is picked up by the maintainer and
pushed into his git tree which is then offered to Linus for pulling it
into mainline. We add a Cc: stable@kernel.org tag to the commit, which
triggers a notifier to the stable kernel team when the patch hits
Linus tree.

Thanks,

	tglx

  reply	other threads:[~2009-10-07 11:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 16:32 Steven Noonan
2009-10-06  7:31 ` Eero Nurkkala
2009-10-06 10:22   ` Steven Noonan
2009-10-06 10:43     ` Eero Nurkkala
2009-10-06 11:22       ` Steven Noonan
2009-10-06 12:36         ` Eero Nurkkala
2009-10-07  0:54           ` Steven Noonan
2009-10-07  1:22             ` Steven Noonan
2009-10-07  5:27               ` Eero Nurkkala
2009-10-07  7:30                 ` Steven Noonan
2009-10-07  7:49                   ` Eero Nurkkala
2009-10-07  8:05                     ` Steven Noonan
2009-10-07  8:11                       ` Steven Noonan
2009-10-07  8:14                       ` Eero Nurkkala
2009-10-07  8:24                         ` Steven Noonan
2009-10-07  8:43                           ` Eero Nurkkala
2009-10-07  8:52                             ` Steven Noonan
2009-10-07  9:31                               ` Eero Nurkkala
2009-10-07 10:42                                 ` Thomas Gleixner
2009-10-07 11:03                                   ` Steven Noonan
2009-10-07 11:15                                     ` Thomas Gleixner [this message]
2009-10-07 11:06                                 ` [tip:timers/urgent] NOHZ: update idle state also when NOHZ is inactive tip-bot for Eero Nurkkala
2009-10-07 13:35                                   ` Rik van Riel

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=alpine.LFD.2.00.0910071306300.9428@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=ext-eero.nurkkala@nokia.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=riel@redhat.com \
    --cc=steven@uplinklabs.net \
    --cc=venkatesh.pallipadi@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®