lkml.org 
[lkml]   [2009]   [Dec]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [tip:tracing/urgent] tracing: Fix event format export

* Johannes Berg <johannes@sipsolutions.net> wrote:

> On Thu, 2009-12-03 at 15:55 +0100, Ingo Molnar wrote:
>
> > > Any reason that this did not make it into Mainline? 2.6.32 is out, and
> > > Johannes Berg was depending on this for his users.
> >
> > Yeah, it narrowly missed the last -rc (-rc8), and we only push
> > post-final-rc fixes for serious show-stopper regressions.
>
> You have an interesting definition of "narrowly missed":
>
> $ git show v2.6.32-rc8
> ...
> Date: Thu Nov 19 14:32:50 2009 -0800
> ...
> $ git show --pretty=fuller 811cb50baf63461ce0bdb234927046131fc7fa8b
> ...
> CommitDate: Fri Nov 13 22:20:34 2009 -0500

Yes, it came in late, after -rc7 and just two weeks before the final
2.6.32 kernel was released. Please test linux-next or -tip more
frequently if you want fixes to go upstream sooner.

> And Steven's pull request for this very simple fix was from the 14th.
> That's 5 days until -rc8.

We are extra careful in late -rc's - and per Linus's request we are only
pushing fixes for serious regressions, and even those we only push after
careful testing. That's a few days commit life-time at minimum in the
usual case.

> So maybe I have a personality problem, but suck it up -- you're wrong
> this time.

No need to complain - the fix is upstream now and will be in 2.6.32.1 -
within 1-2 weeks. If that's not fast enough for you then you can
cherry-pick upstream commit 811cb50baf63461ce0bdb234927046131fc7fa8b
into your tree right now.

Thanks,

Ingo


\
 
 \ /
  Last update: 2009-12-06 18:13    [W:0.039 / U:2.988 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site