From: Krzysztof Halasa <khc@pm.waw.pl>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Seth Heasley <seth.heasley@intel.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Tejun Heo <tj@kernel.org>
Subject: Re: JMB363 false hotplug detections
Date: Sat, 16 Jan 2010 19:34:22 +0100 [thread overview]
Message-ID: <m3wrzh3nm9.fsf@intrepid.localdomain> (raw)
In-Reply-To: <51f3faa71001161010m47d885cfx5d17486016476ed5@mail.gmail.com> (Robert Hancock's message of "Sat, 16 Jan 2010 12:10:08 -0600")
Robert Hancock <hancockrwd@gmail.com> writes:
> What revision does your JMB363 report in lspci? Mine shows:
>
> 03:00.0 SATA controller: JMicron Technologies, Inc. 20360/20363 Serial
> ATA Controller (rev 03) (prog-if 01 [AHCI 1.0])
Same here.
--
Krzysztof Halasa
next prev parent reply other threads:[~2010-01-16 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 18:10 JMB363 false hotplug detections (was: ahci: AHCI and RAID mode SATA patch for Intel Cougar Point DeviceIDs) Robert Hancock
2010-01-16 18:34 ` Krzysztof Halasa [this message]
2010-01-17 2:07 ` Tejun Heo
2010-01-17 20:19 ` JMB363 false hotplug detections Krzysztof Halasa
2010-01-19 8:57 ` 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=m3wrzh3nm9.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=hancockrwd@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.heasley@intel.com \
--cc=tj@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).