mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ray Lee" <ray-lk@madrabbit.org>
To: Dan <metalifloyd@gmail.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: PROBLEM: SATA AHCI driver significant throughput loss in 2.6.22-rc5-g75154f40-dirty
Date: Sun, 1 Jul 2007 10:33:12 -0700	[thread overview]
Message-ID: <2c0942db0707011033v21c91584h3924402f0ce30fa5@mail.gmail.com> (raw)
In-Reply-To: <439fa30707010956h1c467e28xc9eff37ebec523ad@mail.gmail.com>

On 7/1/07, Dan <metalifloyd@gmail.com> wrote:
> > Are you able (as a matter of some urgency) to run a git bisection
> > search to identify the offending commit?
>
> For some reason I am no longer able to reproduce the problem. I've
> tried several versions including the one I reported and I just can't
> reproduce the problem. I accidentally overwrote the original kernel
> that had the problem. The weird thing is even when I reset the git
> tree to 2.6.22-rc5-g75154f40 and build it, the error is gone.

But that isn't the kernel you reported the error against. You reported
that 2.6.22-rc5-g75154f40-*dirty* had the error, which means there was
a diff between what you were building and what was in the repository.
If you know what the diff was and it was something trivial, then you
can disregard this bit of pedantry, but if not, try to recall if you
had something else patched against that.

Regardless, as it's not reproducible it sounds like the report should
be closed...

      reply	other threads:[~2007-07-01 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27  4:17 Dan
2007-06-29 13:36 ` Michal Piotrowski
2007-07-03  8:24   ` Tejun Heo
2007-06-30  7:57 ` Andrew Morton
2007-07-01 16:56   ` Dan
2007-07-01 17:33     ` Ray Lee [this message]

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=2c0942db0707011033v21c91584h3924402f0ce30fa5@mail.gmail.com \
    --to=ray-lk@madrabbit.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=metalifloyd@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®