public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Vince Weaver <vince@deater.net>
Cc: Christoph Hellwig <hch@infradead.org>,
	Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org, acme@infradead.org,
	Andi Kleen <ak@linux.intel.com>,
	Namhyung Kim <namhyung.kim@lge.com>,
	peterz@infradead.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] RFC: perf, tools: Move gtk browser into separate perfgtk executable
Date: Tue, 13 Aug 2013 18:04:24 +0200	[thread overview]
Message-ID: <20130813160424.GC5280@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1308130955360.4537@pianoman.cluster.toy>


* Vince Weaver <vince@deater.net> wrote:

> On Tue, 13 Aug 2013, Ingo Molnar wrote:
> > * Vince Weaver <vince@deater.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

  reply	other threads:[~2013-08-13 16:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05  2:22 [PATCH] RFC: perf, tools: Move gtk browser into separate perfgtk executable Andi Kleen
2013-08-05  8:16 ` Ingo Molnar
2013-08-05  8:23   ` Christoph Hellwig
2013-08-05  8:31     ` Ingo Molnar
2013-08-05  8:34       ` Christoph Hellwig
2013-08-05  9:08         ` Ingo Molnar
2013-08-06  6:19           ` Christoph Hellwig
2013-08-12 18:19             ` Ingo Molnar
2013-08-12 19:25               ` Vince Weaver
2013-08-13 10:48                 ` Ingo Molnar
2013-08-13 12:11                   ` Arnaldo Carvalho de Melo
2013-08-13 16:00                     ` Ingo Molnar
2013-08-13 21:57                       ` Vince Weaver
2013-08-13 22:17                         ` Andi Kleen
2013-08-14 14:13                         ` Arnaldo Carvalho de Melo
2013-08-14 14:20                           ` Ingo Molnar
2013-08-13 14:03                   ` Vince Weaver
2013-08-13 16:04                     ` Ingo Molnar [this message]
2013-08-05  9:08     ` Namhyung Kim
2013-08-05  9:12       ` Ingo Molnar
2013-08-05  9:18         ` Pekka Enberg
2013-08-05 19:10       ` Andi Kleen

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=20130813160424.GC5280@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@infradead.org \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vince@deater.net \
    /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