From: Ingo Molnar <mingo@kernel.org>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: update_rq_clock() must skip ONE update
Date: Tue, 1 Apr 2014 11:55:48 +0200 [thread overview]
Message-ID: <20140401095548.GB1299@gmail.com> (raw)
In-Reply-To: <1396322880.5324.37.camel@marge.simpson.net>
* Mike Galbraith <umgwanakikbuti@gmail.com> wrote:
> On Mon, 2014-03-31 at 11:37 -0700, Linus Torvalds wrote:
> > On Mon, Mar 31, 2014 at 11:27 AM, Mike Galbraith
> > <umgwanakikbuti@gmail.com> wrote:
> > >
> > > Oh, I didn't cc you because I wanted it applied instantly as ultra
> > > critical, only because the chain of events might be of interest.
> >
> > Ok. That was my main worry, since I was in the process or releasing
> > 3.14, and I just couldn't tell if the patch was something I should
> > worry about or not.
> >
> > And it seems that not applying it was the right thing, which is all
> > that matters by now.
>
> Yes. Jocular red flag was to Peter and Ingo. I don't try to bypass
> them, that would be plain rude. I've been known to help maintainers
> a little, but I don't ever try to call the shots. They do that
> well.
Btw., in general feel free to Cc: Linus if a fix looks truly urgent,
as neither Peter nor me might be around on a weekend, shortly before a
release.
Thanks,
Ingo
next prev parent reply other threads:[~2014-04-01 9:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 7:24 [PATCH] sched: update_rq_clock() must skip ONE update Mike Galbraith
2014-03-31 0:12 ` Linus Torvalds
2014-03-31 4:20 ` Mike Galbraith
2014-03-31 16:00 ` Steven Rostedt
2014-04-01 3:10 ` Mike Galbraith
2014-04-01 3:26 ` Steven Rostedt
2014-03-31 16:13 ` Linus Torvalds
2014-03-31 18:27 ` Mike Galbraith
2014-03-31 18:37 ` Linus Torvalds
2014-04-01 3:28 ` Mike Galbraith
2014-04-01 9:55 ` Ingo Molnar [this message]
2014-04-03 8:02 ` Mike Galbraith
2014-04-08 15:53 ` Peter Zijlstra
2014-04-08 16:56 ` Mike Galbraith
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=20140401095548.GB1299@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=umgwanakikbuti@gmail.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