From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: ahci: improve and limit spurious interrupt messages, take#3
Date: Thu, 25 Jan 2007 21:04:52 -0500 [thread overview]
Message-ID: <45B961C4.10404@pobox.com> (raw)
In-Reply-To: <20070125101628.GA8606@htj.dyndns.org>
Tejun Heo wrote:
> + const u32 *f = pp->rx_fis + RX_FIS_SDB;
> +
> + ata_port_printk(ap, KERN_INFO, "Spurious SDB FIS during NCQ "
> + "issue=0x%x SAct=0x%x FIS=%08x:%08x%s\n",
> + readl(port_mmio + PORT_CMD_ISSUE),
> + readl(port_mmio + PORT_SCR_ACT), f[0], f[1],
Direct access to f[] would appear to be an endian problem...
Jeff
next prev parent reply other threads:[~2007-01-26 2:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 9:01 [PATCH] ahci: improve and limit spurious interrupt messages Tejun Heo
2007-01-16 6:52 ` [PATCH] ahci: improve and limit spurious interrupt messages, take#2 Tejun Heo
2007-01-25 1:24 ` Jeff Garzik
2007-01-25 7:55 ` Tejun Heo
2007-01-25 10:16 ` ahci: improve and limit spurious interrupt messages, take#3 Tejun Heo
2007-01-25 22:24 ` Jeff Garzik
2007-01-26 2:04 ` Jeff Garzik [this message]
2007-01-26 5:47 ` [PATCH] ahci: fix endianness in spurious interrupt message Tejun Heo
2007-01-26 22:24 ` Jeff Garzik
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=45B961C4.10404@pobox.com \
--to=jgarzik@pobox.com \
--cc=htejun@gmail.com \
--cc=linux-ide@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.