Prev: [RFC,PATCH 0/2] Common struct clk implementation, v4
Next: [git pull] Input updates for 2.6.35-rc1
From: Christoph Hellwig on 4 Jun 2010 03:50

Not sure what the rules for new tracepoints are, but in addition to the
fixes I'd really love to see the tracepoints in 2.6.35.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Dave Chinner on 7 Jun 2010 20:20
On Fri, Jun 04, 2010 at 03:49:38AM -0400, Christoph Hellwig wrote:
>
> Not sure what the rules for new tracepoints are, but in addition to the
> fixes I'd really love to see the tracepoints in 2.6.35.

Personally I think they are just as important (or even more
important) than the bug fixes because we seem to break this code
regularly because nobody can clearly see what the internals are
doing to verify their change is working correctly.

Cheers,

Dave.
--
Dave Chinner
david(a)fromorbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Christoph Hellwig on 8 Jun 2010 04:10
On Tue, Jun 08, 2010 at 10:11:15AM +1000, Dave Chinner wrote:
> On Fri, Jun 04, 2010 at 03:49:38AM -0400, Christoph Hellwig wrote:
> >
> > Not sure what the rules for new tracepoints are, but in addition to the
> > fixes I'd really love to see the tracepoints in 2.6.35.
>
> Personally I think they are just as important (or even more
> important) than the bug fixes because we seem to break this code
> regularly because nobody can clearly see what the internals are
> doing to verify their change is working correctly.

Given that Linus is pretty strict about only taking regression fixes
I'd rather get the regression fix in and miss out on the tracing until
the next merge window then missing out on everything.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [RFC,PATCH 0/2] Common struct clk implementation, v4
Next: [git pull] Input updates for 2.6.35-rc1