mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Voluspa <lista1@telia.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, rajesh.shah@intel.com,
	kjarvel@home.se, howarth@bromo.msbb.uc.edu
Subject: Re: PCI error on x86_64 2.6.13 kernel
Date: Sat, 19 Nov 2005 13:05:48 +0100	[thread overview]
Message-ID: <20051119130548.1d86e1d9.lista1@telia.com> (raw)
In-Reply-To: <20051119011840.GB28175@kroah.com>

On Fri, 18 Nov 2005 17:18:40 -0800 Greg KH wrote:
> Is there any way you could be able to run 'git bisect' between 2.6.12
> and 2.6.13 to try to find the offending changeset?  I would really
> appreciate it.

I'll take one beer (or in .ru: \u043f\u0438\u0432\u043e) for each hour ;-) This is a six-pack:

299de0343c7d18448a69c635378342e9214b14af is first bad commit
diff-tree 299de0343c7d18448a69c635378342e9214b14af (from 90b54929b626c80056262d9d99b3f48522e404d0)

Marvellous tool, that git. But it took less time - for us users - when we only had to
wave in a general -rc direction...

I've not tried to back the commit out from a 2.6.14 kernel, though. Will wait for a real fix.

Mvh
Mats Johannesson
--

  parent reply	other threads:[~2005-11-19 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18  7:04 Voluspa
2005-11-19  1:18 ` Greg KH
2005-11-19  5:06   ` Voluspa
2005-11-19 12:05   ` Voluspa [this message]
     [not found] <fa.gf7dlu0.a4g9qo@ifi.uio.no>
2005-10-26 21:06 ` Niklas Kallman
2005-11-18  0:24   ` Rajesh Shah
  -- strict thread matches above, loose matches on Subject: below --
2005-10-26 13:53 Jack Howarth

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=20051119130548.1d86e1d9.lista1@telia.com \
    --to=lista1@telia.com \
    --cc=greg@kroah.com \
    --cc=howarth@bromo.msbb.uc.edu \
    --cc=kjarvel@home.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rajesh.shah@intel.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

Powered by JetHome