From: Jeff Garzik <jgarzik@pobox.com>
To: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
rdunlap@xenotime.net
Subject: Re: [patch 2/2] libata: _SDD support
Date: Wed, 27 Sep 2006 18:54:07 -0400 [thread overview]
Message-ID: <451B010F.4010308@pobox.com> (raw)
In-Reply-To: <20060927153634.716a8aa1.kristen.c.accardi@intel.com>
Kristen Carlson Accardi wrote:
> + /* Don't continue if not a SATA device. */
> + if (!ata_id_is_sata(atadev->id)) {
> + if (ata_msg_probe(ap))
> + ata_dev_printk(atadev, KERN_DEBUG,
> + "%s: ata_id_is_sata is False\n", __FUNCTION__);
> + goto out;
> + }
I forgot to note this in patch #1, so this comment applies to both patch
#1 and patch #2:
ata_id_is_sata() is probably not the check you want. This tests Word 93
of IDENTIFY DEVICE output, which is a check that's not in the ATA
specification, but rather something I came up with. It will indicate
false for ATA devices that attach via SATA cables, but have a PATA
bridge chip soldered onto the ATA device.
A better test is probably "ap->cbl == ATA_CBL_SATA".
> +EXPORT_SYMBOL_GPL(ata_acpi_push_id);
Remove the export, this is for exporting symbols to export kernel
modules, not for making symbols visible at the C level, to other C modules.
Jeff
next prev parent reply other threads:[~2006-09-27 22:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060927223441.205181000@localhost.localdomain>
2006-09-27 22:36 ` [patch 1/2] libata: _GTF support Kristen Carlson Accardi
2006-09-27 22:49 ` Jeff Garzik
2006-10-09 11:41 ` Stefan Seyfried
2006-10-09 15:10 ` Randy Dunlap
2006-09-27 22:36 ` [patch 2/2] libata: _SDD support Kristen Carlson Accardi
2006-09-27 22:54 ` Jeff Garzik [this message]
[not found] <20060928182211.076258000@localhost.localdomain>
2006-09-28 18:29 ` Kristen Carlson Accardi
2006-09-29 2:13 ` Matthew Garrett
2006-09-30 0:33 ` Kristen Carlson Accardi
2006-10-02 13:08 ` Pavel Machek
2006-09-28 18:30 ` Kristen Carlson Accardi
2006-09-29 17:56 ` Valdis.Kletnieks
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=451B010F.4010308@pobox.com \
--to=jgarzik@pobox.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.