[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130813160424.GC5280@gmail.com>
Date: Tue, 13 Aug 2013 18:04:24 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Vince Weaver <vince@...ter.net>
Cc: Christoph Hellwig <hch@...radead.org>,
Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
acme@...radead.org, Andi Kleen <ak@...ux.intel.com>,
Namhyung Kim <namhyung.kim@....com>, peterz@...radead.org,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] RFC: perf, tools: Move gtk browser into separate perfgtk
executable
* Vince Weaver <vince@...ter.net> wrote:
> On Tue, 13 Aug 2013, Ingo Molnar wrote:
> > * Vince Weaver <vince@...ter.net> wrote:
>
> > In the past you used to only test your library once the -stable kernel was
> > released - has this changed recently by any chance? I remember that in one
> > particular case I got a regression bugreport from you essentially on the
> > day of a -stable release.
> >
> > If you tested -rc2 or so that would give us a much larger window to
> > fix any breakages that affect your library. (I'm not even asking for
> > linux-next testing.)
>
> I wasn't aware that the Linux "no-ABI breakage guarantee" only applied
> to people who ran -rc kernels.
It obviously does not, and nowhere did I claim the opposite.
> I've spent a lot of time enhancing trinity and writing my own perf
> syscall fuzzer just to try to keep on top of ABI breaks as per your
> rules and they still slip in and they still don't get reverted.
Your fuzzing effort is much appreciated, but please don't mix this up with
the other ABI bugs you were talking about:
> > > > I've had perf ABI changes break programs I maintain at least three
> > > > times in the last 2 kernel releases.
We can only fix regressions after they get reported.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists