mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Bj?rn Steinbrink <B.Steinbrink@gmx.de>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, Andi Kleen <ak@suse.de>,
	Stephane Eranian <eranian@hpl.hp.com>
Subject: Re: 2.6.22-rc7: known regressions with patches
Date: Tue, 3 Jul 2007 14:42:25 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.98.0707031441480.9434@woody.linux-foundation.org> (raw)
In-Reply-To: <20070703213614.GA29175@atjola.homenet>



On Tue, 3 Jul 2007, Bj?rn Steinbrink wrote:

> On 2007.07.03 18:45:24 +0200, Michal Piotrowski wrote:
> > Subject    : OProfile issues
> > References : http://lkml.org/lkml/2007/6/12/207
> > Submitter  : Stephane Eranian <eranian@hpl.hp.com>
> > Handled-By : Björn Steinbrink <B.Steinbrink@gmx.de>
> > Patch      : http://lkml.org/lkml/2007/6/12/392
> >              http://lkml.org/lkml/2007/6/20/275
> >              http://lkml.org/lkml/2007/6/20/276
> > Status     : patches were suggested
> 
> Andi said that one of the regression fixes wasn't critical for .22 and
> that he wants to do a stopgap for the other regression (my patch
> sucked), reverting the code to the .21 version. So you can drop the
> patches and/or me here.

Can you say which patch should be reverted. This thing really shouldn't 
have gone on this long, I would have hopef we had the oprofile thing 
sorted out already..

		Linus

  reply	other threads:[~2007-07-03 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 16:45 Michal Piotrowski
2007-07-03 20:57 ` Linus Torvalds
2007-07-03 21:36 ` Björn Steinbrink
2007-07-03 21:42   ` Linus Torvalds [this message]
2007-07-03 22:12     ` Björn Steinbrink
2007-07-03 23:38       ` Andi Kleen
2007-07-04  1:12         ` Linus Torvalds

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=alpine.LFD.0.98.0707031441480.9434@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=B.Steinbrink@gmx.de \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=eranian@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@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

all inboxes | Powered by JetHome®