From: Jeff Garzik <jgarzik@pobox.com>
To: Jens Axboe <axboe@suse.de>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] AHCI PCI MSI support, update 1
Date: Wed, 01 Jun 2005 01:46:27 -0400 [thread overview]
Message-ID: <429D4BB3.6080903@pobox.com> (raw)
In-Reply-To: <20050601054422.GA1441@suse.de>
Jens Axboe wrote:
> System boots and works fine (typing this message here), MSI is enabled.
> I double checked with an added printk :-)
Any chance you could post a full /proc/interrupts output for this box?
> So that's at least one ACK for you. Now running NCQ and MSI enabled
> ahci, I'm not sure SATA gets any better!
<grin>
Thanks,
Jeff
next prev parent reply other threads:[~2005-06-01 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 15:57 [PATCH] AHCI PCI MSI support, update 1 Jeff Garzik
2005-06-01 5:44 ` Jens Axboe
2005-06-01 5:46 ` Jeff Garzik [this message]
2005-06-01 5:52 ` Jens Axboe
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=429D4BB3.6080903@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).