All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Tejun Heo <htejun@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	ide <linux-ide@vger.kernel.org>,
	l.genoni@oltrelinux.com, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: something strange in libata-core.c for kernel 2.6.22-rc3
Date: Mon, 21 May 2007 05:41:40 -0400	[thread overview]
Message-ID: <46516954.6030608@garzik.org> (raw)
In-Reply-To: <46515983.6030206@shaw.ca>

Stupid BIOS crap like that is largely the reason why I am reluctant to 
merge pata_acpi.  There is a lot of knowledge like this yet to be 
discovered.

I would feel far more comfortable disassembling the AML like you are 
doing...

	Jeff




  parent reply	other threads:[~2007-05-21  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.MCe9nCgx+WnsHp+weZyM9LiDF0s@ifi.uio.no>
     [not found] ` <fa.rv8/6n3uBnAIoUHHNUW3eR7cJd8@ifi.uio.no>
     [not found]   ` <fa.LXy58QwLlPXDhsfVUU9kEfA3QbI@ifi.uio.no>
2007-05-20 17:18     ` something strange in libata-core.c for kernel 2.6.22-rc3 Robert Hancock
     [not found]     ` <fa.Ldjy2OubeKomZD0OV2gRm/wpUFo@ifi.uio.no>
2007-05-20 22:27       ` Robert Hancock
2007-05-21  8:34       ` Robert Hancock
2007-05-21  9:09         ` Tejun Heo
2007-05-21 11:15           ` Alan Cox
2007-05-21 18:14             ` Robert Hancock
2007-05-21  9:41         ` Jeff Garzik [this message]
     [not found] <Pine.LNX.4.64.0704181704270.1663@Phoenix.oltrelinux.com>
     [not found] ` <20070418162525.423b2e7e@the-village.bc.nu>
2007-05-20 12:40   ` l.genoni
2007-05-20 17:31     ` Tejun Heo

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=46516954.6030608@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hancockr@shaw.ca \
    --cc=htejun@gmail.com \
    --cc=l.genoni@oltrelinux.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.