All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Brad Campbell <brad@wasp.net.au>
Cc: linux-ide@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] libata ATA vs SATA detection and workaround.
Date: Mon, 30 Aug 2004 13:59:42 -0400	[thread overview]
Message-ID: <41336B0E.1090000@pobox.com> (raw)
In-Reply-To: <41336141.7010407@wasp.net.au>

Brad Campbell wrote:
> Pretty new at kernel code. (And C for that matter)

Since you've been so helpful, I choose to disbelieve this ;-)


> I did note that it appears it's not going to do the right thing if we 
> have more than one device per host, but I guess thats not going to be an 
> issue for SATA for the near future anyway.
> 
> How's this grab you?

Looks perfect.

Confirm for me that it solves your problem, and I'll push it upstream.

	Jeff

  reply	other threads:[~2004-08-30 17:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-29 17:09 libata dev_config call order wrong Brad Campbell
2004-08-29 17:29 ` Jeff Garzik
2004-08-29 17:47   ` Brad Campbell
2004-08-29 17:59     ` Jeff Garzik
2004-08-29 18:25       ` Jeff Garzik
2004-08-29 18:59         ` Alan Cox
2004-08-30  9:12           ` Brad Campbell
2004-08-30 13:22             ` Alan Cox
2004-08-30 14:38               ` Brad Campbell
2004-08-30 14:42         ` [PATCH] libata ATA vs SATA detection and workaround Brad Campbell
2004-08-30 14:57           ` Brad Campbell
2004-08-30 14:57             ` Brad Campbell
2004-08-30 16:06             ` Jeff Garzik
2004-08-30 16:34               ` Brad Campbell
2004-08-30 16:37                 ` Jeff Garzik
2004-08-30 17:17                   ` Brad Campbell
2004-08-30 17:59                     ` Jeff Garzik [this message]
2004-08-31  7:47                       ` Brad Campbell

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=41336B0E.1090000@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=brad@wasp.net.au \
    --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.